Same pool. Atlassian's usage-based pricing FAQ: "Automation steps: Yes, steps running in sandbox count toward your allowance." No separate sandbox allowance, test runs burn steps like any other run.
Sandbox and production aren't split in the dashboard either, Insights > Platform usage shows one number, and the usage limits you set cap both. Assets objects are the exception, sandbox doesn't count there.
Every trigger, condition, action, branch and loop is a step. A trigger that doesn't match still costs one. Chatty test rules add up fast.
That’s a disastrous change! 😤 Guess I’m disabling all sandbox automation rules right away! Haaaash! 😮💨
One question, though: if a trigger has multiple conditions configured within it, are they counted as a single step for the trigger, plus one step per condition? Or are all the trigger conditions counted together as a single step?
Hi @Priyanka Agrawal
Multiple conditions within the same trigger count as one trigger step, while separate condition components are counted individually when executed. For more details, see Atlassian's explanation of the counting mechanism. https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/
Interestingly, Atlassian is also tracking COMMERCE-151 (Gathering Interest), requesting that triggers without subsequent actions shouldn't consume steps.
Best,
Arek🤠🧙♂️
That's helpful to know. Thanks for sharing COMMERCE-151 as well.
Nothing to thanks. We are here to help :)
Another question: How are automation steps counted in an If/Else block? If the Else branch executes, are the steps in the If branch also counted, and vice versa? Also, if the condition is met in the first If block, are only the steps in that block counted, or are the steps in the remaining branches counted as well?
Only the branch that runs, plus the checks on the way down to it. Built one on a test site, If / Else-if / Else with 2 actions each, and ran every path once.
If path logged 5. Trigger, the if/else block, the If condition, 2 actions. Else-if logged 6 because the If got checked first, Else logged 7. Actions in branches that didn't run weren't in the log at all.
Order matters then. Most common branch on top.
That's the audit log per run though. Atlassian's usage doc counts every trigger, condition, action, branch and loop that runs as a step, which matches, but I didn't watch Platform usage move for it.
Hi @Priyanka Agrawal, Sandbox and production automation usage are completely separate. Testing in a sandbox will never consume your production rule executions.
Thanks!!
I confirmed with the Atlassian support that automation steps consumed within a Jira sandbox are included in the organization-level platform usage total. Since the allowance is pooled at the organization level, usage from all linked sites, including sandboxes contributes to the cumulative total shown in the Atlassian Administration > Insights > Platform usage report.
It looks like you're new here. Sign in or register to get started.
