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 time one of these components runs, it counts as one step:
Triggers – The event that kicks off your flow.
Conditions – The logic that decides whether the flow should keep going.
Actions – The actual task your flow performs.
Branches (if/else) – Different paths your flow can take based on logic.
Loops (for each) – A set of actions that repeats within a single flow.
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.SOME_ERRORS: Business errors, such as a flow misconfiguration.ABORTED: The step was stopped before completion.NO_MATCH: Even if a trigger doesn't find a match to start the rest of the flow, the trigger execution itself is charged as one step.
What doesn’t count as an automation step?
System and synthetic components we run on your behalf.
THROTTLEDruns where no step actually executes, and system-side errors.
Agentic components like Use Rovo, Use agent, or Use Jira Coding agent are billed separately under Rovo credits and do not consume 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 |
チームワーク コレクション | 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 |
How to view your usage
Organization admins can track step usage in Atlassian Administration.
To view your usage:
アトラシアンの管理に移動します。複数の組織がある場合は、対象の組織を選択します。
Select Insights, then Platform usage.
From here you can view your available steps against your total organization level allowance.
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.
この内容はお役に立ちましたか?