I’m trying to prevent an error return (500) to Keap when our server gets swamped by HTTP POST requests from one of our Keap contact notification Automations. The requests arrive withing the same millisecond. Some requests are hampered by a database lock on our server while it records the POST for later processing. This lock results in a 500 response to Keap.
I’m thinking of moving modifying the Automation to send the POST after a time delay that is between two target date/times 15 minutes apart, rather than at that target date/time.
Will this spread the POSTS through that time range or will the POSTS still happen at the start of that time duration?
If you have a delay timer that is ‘between’, it will trigger at the first time available in that timeframe. For example, if you say run between 8a-5p and you have 100 posts that should go out during the night, at 8a, they will all trigger.
Here is a great tool that can accomplish what you are trying to do: PlusThis Throttler
You can set it so that it will only pull X contacts per X timeframe - allowing you to set up a delay timers to say “only run between 8a-5p”, then throttle saying only send 2 per minute (or whatever), and then it will send the posts across in a spaced out manor. You could always do the same with Make or Zapier, but the PlusThis tool has the simplest UI.
Jeff
Thanks for the quick reply!
