The queue is an important part of our API as it helps to manage the availability of resources.

Understanding the queue

---

API requests to trigger automations that are received after you have hit your subscriptions concurrency limit will enter a queue. This queue will be processed every 5 minutes from when the automation enters the queue - these will not immediately run when another automation has finished and your account has the ability to run another automation. These will continue to be processed every 5 minutes until there is no run requests left to process.

For example, if 4 requests enter the queue at 1:00pm and your concurrency limit is 2 bots, 2 of these will be processed at 1:05pm and the other two at 1:10pm. These times are representative and may vary based on when the requests enter the queue and resources available, the delay may at times be longer than 5 minutes but should be less than 10 minutes - we recommend ensuring that this is taken into account for time sensitive automations.

There are limitations that you should be aware of when using our queue system:

• There is a limit of 10 requests per automation.
• Requests can not be removed from the queue, or their place in the queue modified.

In rare cases, if resources are temporarily unavailable to run your automation, it may get added to the queue.