Automation Step Allowance: Do Automations Stop Before Extra Usage Billing Starts?

On the published pages the steps pause is a December problem. Atlassian's own wording: "Allowance limits and billing for these meters will go into effect on December 3, 2026." The licensing page adds that the exact date varies by capability and billing cadence. Nobody has written the sentence "the steps pause is not enforced before then" though. So check it, don't assume it. Atlassian Administration, Insights, Platform usage shows the steps meter with allowance, usage and the reset date.

What could stop flows this month is the older runs cap. The automation limits KB still describes a monthly cap on successful rule runs that stops every rule in the product until the 1st. The usage calc doc says the meter has moved to steps. Two docs, two stories. The Usage tab under Automation flows shows which one you're actually on.

The "has moved to steps" line in the usage calc doc describes the metering model. Probably the source of the confusion.

@Neo Apps ,

@Mihai_LeanZero has the first half exactly right, with the doc quote: with extra usage off, hitting 100 percent stops every flow until your usage billing date, and that date is your subscription's date, not the first of the month. Let me take the second half of your question, whether to enable extra usage now, because the useful answer is "yes, with a limit, and then make sure you never need it."

Enable it, but set a spend limit the same minute. Extra usage is on by default in Atlassian's model and billed in arrears (how usage-based pricing works); if yours shows as off, an admin disabled it or set a zero limit. Atlassian Administration, Insights, Platform usage, select the Automation steps meter, then "Get more usage" and Enable extra usage, and set a monthly limit right after. That turns the December cliff into a capped overage instead of a silent stop, and the 80 and 100 percent notifications go to org and billing admins so someone sees it coming.

Then find out what is spending 172,100 steps, because it is usually three rules. The same Platform usage page shows consumption per app, and the Automation usage view shows it per rule. A step is every component that runs: trigger, each condition, each action, each branch, and each loop iteration (how usage is calculated). Two consequences people miss:

1. A rule that fires and does nothing still pays. A "Work item updated" trigger with a condition that fails 95 percent of the time spends a trigger step and a condition step on every update across the space. Swap the trigger for the narrow one ("Field value changed" for the specific field) and the same rule costs a fraction.
2. Scheduled rules with broad JQL are the other big spender. A rule that runs every hour over 2,000 items and branches per item spends thousands of steps a day even when nothing changes. Tighten the JQL in the trigger (updated >= -1h), lengthen the interval, or move the check into an event-driven rule.

Order your conditions so the cheapest and most selective is first, because a failed first condition stops the count there. In most estates I have looked at, the top three rules by steps account for well over half the total, and each has one of those two shapes.

One thing that does not count: the Rovo agent actions inside rules are metered as Rovo credits, not steps, so if your rules use them, that is a separate meter to watch on the same page.

Yes, they stop. Straight from the usage docs: "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."

The billing date part catches people out. Not the first of the month. The usage billing date. A 3 December reset, with the allowance crossed on 20 November, means roughly two weeks of no automation at all.

With extra usage enabled the docs say admins are notified at 80% and 100%, flows keep running, and the overage lands on the next invoice.

Enabling it early costs nothing until the allowance is actually crossed. It removes the cliff.