How is my usage calculated?
How is my automation usage calculated?
Automation usage is measured by the number of flows that run each month.
Usage limits vary by app and plan, but they always reset at the beginning of each month. Unused runs from the previous month will not roll over.
What counts as a flow run?
When an automation flow runs successfully, that is, it performs at least one action, it counts as a run. Each successful flow run counts only once toward usage, even if the flow performs multiple actions.
What doesn’t count as a flow run?
Flows that perform no actions
If a flow runs, but doesn’t successfully perform an action, then it won’t count towards your monthly usage. For example, let’s say we had the following flow set up in Confluence:
Trigger: When a page is published
Condition: If
{{page.title}}containsRetroAction: Then add a label,
Sprint retro notes
The flow will trigger every time a page is published, however, the run will only count towards your usage if the page title contained Retro and the label Sprint retro notes was added successfully.
Actions that don’t count
The following actions don’t count toward your automation usage:
Log action
Create variable
Create lookup table
Re-fetch work item data
Lookup work items
If your flow runs, but it only performs the above actions, that run won’t count towards your usage.
System flows
In Jira Cloud, some space templates come with automation flows already set up — these are called system flows. When system flows run, they don’t count toward your usage.
Currently, there are no system flows in Confluence.
What are my usage limits?
Usage limits vary by app and plan, but they always reset at the beginning of each month. Unused executions from the previous month will not roll over.
For a limited time, customers on Premium and Enterprise plans will have access to advanced steps within the Atlassian Acceptable Use Policy.
In the future, usage beyond existing usage limits will incur additional charges based on consumption. At that time, organization admins will have tools to monitor and manage consumption and will be able to purchase additional capacity.
Number of flow runs per month | ||||
|---|---|---|---|---|
Free | Standard | Premium | Enterprise | |
Jira | 100 | 1,700 | 1,000 multiplied by the number of users | Unlimited |
Jira Service Management | 500 | 5,000 | 1,000 multiplied by the number of users | Unlimited |
Jira Product Discovery | 200 | 500 | 1,000 multiplied by the number of users | Plan not available for Jira Product Discovery |
Confluence | 10 | 100 | 1,000 multiplied by the number of users | Unlimited |
How flows are billed to each Jira Cloud app
Each automation flow is assigned to an app, and will count toward that app’s monthly limit. This is based on the following criteria:
Flows scoped to a specific space will be billed to the app that space is in.
Flows scoped to a space type will be billed to that app
e.g. if a flow is set to run for all software spaces, it will be assigned to Jira.
Flows scoped to multiple spaces will be assigned to the app that has the highest monthly limit
e.g. Let’s say you’ve signed up for Premium plans for Jira and Jira Service Management. And let’s say you create a flow that runs across all three.
Flows with a Global scope will be billed to the app with the highest automation limit.
How is usage tracked?
On the Usage screen, you’ll find an outline of your monthly automation usage, and how you’re tracking against your plan’s limit.
Learn more about how to access and understand the Usage screen.
What happens if I reach my monthly limit?
If our system predicts that your team will pass your monthly execution limit, you’ll see a warning banner whenever you go to automation. For example, this might happen if you reach 50% of your monthly in the first week.
If your team reaches the limit of allotted executions, your flows will fail to run until usage resets on the first of the following month.
The exception to this is system flows; these flows will always run unless you disable them. Learn more about system flows
When will my monthly limit reset?
Automation usage resets for all apps on the first of each month at 00:00 UTC (universal time coordinated).
Was this helpful?