Try or ByeTry or Bye

Jira Automation Limit Reached (Rules Throttled)

Ongoing Web (Cloud) Updated October 21, 2026

Quick answer

Jira Cloud meters automation in steps per month; when the allowance runs out, rules are throttled until the next cycle. Cut noisy rules or upgrade.

Most likely fix: See what's consuming the allowance.

Symptoms

Admins get emails that rules were throttled; rules stop running late in the month; audit log may misleadingly show 'No actions performed'.

Why it happens

  • Free plan: only 150 automation steps per month for the whole site
  • Standard: 400 steps per user per month
  • Rules triggered on every issue update or bulk operation consuming steps quickly
  • Unlimited single-project rules ended in late 2023

How to fix it

Try these in order — the most common fix is first.

  1. 1. See what's consuming the allowance

    1. Admin > Automation > Usage
    2. Sort rules by executions and find the noisiest ones

  2. 2. Reduce executions

    1. Add conditions early in a rule so it exits before acting
    2. Replace 'Issue updated' triggers with specific field-change triggers
    3. Batch scheduled rules (one JQL run instead of per-issue triggers)
    4. Disable duplicate or unused rules

  3. 3. Upgrade if needed

    1. Premium raises the allowance to 750 steps per user and Enterprise to 1,000
    2. Compare the cost against reworking rules before upgrading every user

This guide also covers

  • jira automation limit
  • jira automation limit reached
  • jira automation throttled
  • jira automation usage

Still not working?

If Jira keeps failing, you're not alone. See every Jira problem users report or the alternatives people switch to.

Other Jira errors