How is your automation usage calculated
Atlassian Automation has moved from per app monthly flow limits to usage-based automation steps pooled at the organization level. This means your total usage is the sum of all automation steps across your Atlassian apps. See How usage-based pricing works.
On December 3, 2026, extra usage billing takes effect. In Atlassian Administration, you can track your organization's usage and plan ahead.
Automation usage is measured in steps. An automation step is a single executed part of an automation flow, including triggers, conditions, actions, branches, and loops.
Your organization receives included automation step allowances based on your subscriptions and plan, pooled at the organization level.
For example, if your organization has:
100 Jira Premium users: 100 x 750 = 75,000 steps
100 Confluence Standard users: 100 x 100 = 10,000 steps
Total monthly allowance: 85,000 steps (shared across both apps)
Every trigger, condition, action, branch, and loop that runs in a flow counts as a step toward your usage. Allowances refresh monthly.
What counts as an automation step?
A step is a metered feature that runs within an automation flow. Each of these counts as one step when it runs. Loops and branches count once, however many items they go through:
Step | What it does | How it’s counted |
|---|---|---|
Trigger | The event that kicks off your flow. | One step each time it runs. Conditions set inside the trigger, such as work item transitioned to Done, are part of that one step and don’t add steps. |
Condition | The logic that decides whether the flow should keep going. | One step for each condition that executes. If a condition block checks multiple criteria, for example, Priority is High, and Status is Open, it counts as one step. A condition that evaluates to |
Action | The actual task your flow performs. | One step each time it runs. |
Branch (if/else) | Different paths your flow can take based on logic. | One step for the branch, plus the steps in the path that runs. Paths that don't run use zero steps. |
Loop (for each) | A set of actions that repeats within a single flow. | One step for the loop, plus the steps that run inside it for each item. For example, if a loop updates three subtasks with one action each, it counts as four steps total. |
A step is charged if its execution results in any of the following statuses:
SUCCESS: The step completed as intended.NO_ACTIONS_PERFORMED: The step ran but didn't result in a change. For example, a condition wasn't met, so no actions ran.SOME_ERRORS: Business errors, such as a flow misconfiguration. Only the steps that ran before the error count.FAILURE: The flow failed due to a business error, such as a misconfiguration or an external service failure. Only the steps that ran before the failure count.LOOP: The flow stopped because it reached the loop limit. Only the steps that ran before the limit count.
Examples of how steps are counted
Flow run | Step breakdown | Total steps |
|---|---|---|
Condition after the trigger |
| Three steps |
Set the condition inside the trigger |
| Two steps |
If/else branch | Assume the work item is High priority
| Three steps |
Branch with a condition inside the path | Assume the branch processes three related work items, and two are unresolved
| Seven steps |
Loop with an action inside | Assume the loop is set to run three times
| Five steps |
Automation invokes an AI capability |
| Three Automation steps, plus Rovo credits for the AI operation |
What doesn’t count as an automation step?
System steps: Some steps don’t count, even if you add them to your flow. These include
Log action,Create variable,Create lookup table,Re-fetch work item data, andLookup work items.Aborted or throttled runs: No steps are charged, including any steps that ran before the run stopped.
Atlassian system errors: Any step that fails due to an error on Atlassian’s side.
Agentic components like Use Rovo, Use agent, or Use Jira Coding agent are billed separately under Rovo credits and do not consume automation steps. The other steps in the same flow still count toward your automation allowance. Actions that use third-party AI, such as Use Cursor and Use GitHub Copilot, count as automation steps.
What are my automation step allowances?
Your organization’s total step allowance is the sum of all automation steps across your apps.
| Automation step per month | |||
|---|---|---|---|---|
Free | Standard | Premium | Enterprise | |
Jira | 150 per subscription | 400 per user | 750 per user | 1000 per user |
Confluence | 50 per subscription | 100 per user | 250 per user | 500 per user |
Teamwork Collection | 200 per subscription | 2,500 per user | 5,000 per user | 7,500 per user |
Jira Service Management / Service Collection | 1,250 per subscription | 3,000 per user | 6,500 per user | 9,500 per user |
Jira Product Discovery | 100 per subscription | 300 per user | 500 per user | 750 per user |
View your usage
You can view step usage across your whole organization, or by app to see which flows use the most steps.
View usage across your organization
Organization admins can see total step usage in Atlassian Administration.
Go to Atlassian Administration. Select your organization if you have more than one.
Select Usage, then Meters.
Select Automation steps to see your total step usage against your organization’s allowance.
View usage by flow
App admins can see which flows use the most steps in their app.
Jira Cloud and Jira Service Management
In Jira, go to Settings, then System, then Global automation.
Select Usage.
Review your top flows by step usage. Select a flow to open its audit log and see how many steps each run used.
Confluence
In Confluence, go to Settings.
Select Automation under Admin tools, then Usage.
Review your top flows by step usage. Select a flow to open its audit log and see how many steps each run used.
What to expect if you go over your allowance
What happens when you exceed your step allowance depends on your plan. Organization and billing admins set usage limits and have controls to adjust limits as needed.
When you reach your usage limit with extra usage enabled:
Organization and billing admins receive notifications at 80% and 100% usage.
Metered features continue to run without interruption.
Extra usage is charged on your next invoice at the end of the billing period.
Extra usage is billed at $0.50 per 1,000 additional steps. For example, if your organization uses 10,000 steps beyond your included allowance in a given month, the extra usage charge would be $5.00.
If extra usage is disabled and you reach 100% of your total steps allowance, your automation flows will stop running until usage resets on your usage billing date. Organization admins can set a monthly allowance limit to control your spend. See Manage extra usage.
If you need extra usage beyond your total allowance, you can also consider purchasing usage packs.
Was this helpful?