Limits to expect

These limits come from the app itself or from the Atlassian Forge platform it runs on.

AreaLimit
Event-based actionsA 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 guardAn 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 actionsOnce 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 delayDelay in seconds: 1 to 20.
Copy and exportAt most 500 rules from one workflow; at most 10 target workflows per copy; exported text up to 200 KB.
One ruleSettings up to 32 KB; up to 10 expensive Jira operations and a 10,000-character expression.
Shared actionsSteps of one action up to 80 KB.
Limit how manySearch up to 2,000 characters; a limit from 0 to 4,999.
Connect matching work itemsAt most 50 work items per run.
Copy commentsEach file up to 150 MB.
Display message to userShows if the work item page is open, or opened within two minutes of the move.
Run historyKept 90 days. CSV export up to 5,000 rows, newest first.
HistoryKept 90 days.
Forge timeoutsAdmin 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.

Need help with Simple Workflow Automation? Contact us