These limits come from the app itself or from the Atlassian Forge platform it runs on.
| Area | Limit |
|---|---|
| Event-based actions | A new or changed event action can take up to about 3 minutes to start. A wait before running can be 1 to 20 seconds. |
| Loop guard | An event action that starts more than 1,000 times, or makes more than 5,000 changes, in 10 minutes is switched off and Jira administrators are emailed. |
| Scheduled actions | Once a day at a UTC time, within a window of 5 to 180 minutes. At most 50. Work items per run times steps must be 5,000 or fewer. |
| Post-function delay | Delay in seconds: 1 to 20. |
| Copy and export | At most 500 rules from one workflow; at most 10 target workflows per copy; exported text up to 200 KB. |
| One rule | Settings up to 32 KB; up to 10 expensive Jira operations and a 10,000-character expression. |
| Shared actions | Steps of one action up to 80 KB. |
| Limit how many | Search up to 2,000 characters; a limit from 0 to 4,999. |
| Connect matching work items | At most 50 work items per run. |
| Copy comments | Each file up to 150 MB. |
| Display message to user | Shows if the work item page is open, or opened within two minutes of the move. |
| Run history | Kept 90 days. CSV export up to 5,000 rows, newest first. |
| History | Kept 90 days. |
| Forge timeouts | Admin page and rule calls have about 25 seconds; longer work, such as scheduled runs, sequences and emails, runs in the background with up to 15 minutes per step and continues in further steps. |
What this means for you
- Large copies may answer Not done for some workflows when time runs short. Run the copy again for those.
- Post-functions on many work items go to a background queue, so changes can appear a little after the move.
- Conditions and validators run inside Jira and follow Jira’s own limits for Jira expressions.
Related pages
Need help with Simple Workflow Automation? Contact us