- Count conditions, branches, and actions in advanced flows and flow groups.
- Review labels across the whole cloud site.
- Test scheduled searches against real data.
- Measure scheduled run time before tightening the interval.
If you run a dispatch queue on it, those ceilings decide whether your rules keep working. This guide covers five of them and shows how to check each one before it causes trouble.
Most dispatch logic lives in automation rules. A ticket arrives, and a rule assigns it. Another rule raises the priority when the clock runs down. A scheduled search sweeps up anything that slipped through. It works well for months, and then one morning it quietly stops. A rule that used to finish in seconds starts failing. A label list grows past what anyone remembers creating. A search that once returned a handful of items now returns thousands.
You usually find out when a run fails, or when a team lead asks why a ticket sat untouched for a day. The goal here is to check the numbers before they turn into an incident, and to check them again after any large change to the queue. For each limit, I'll explain what it is, why it matters for a queue in particular, and what to look at in your own setup.
A quick note on sources. The Atlassian figures come from its automation service limits page. Atlassian can change those limits, so treat the page as the reference and re-check it on a regular schedule. Nothing in this post replaces testing your own rules against your own volumes.