Most Trello automations that “stop working” haven’t broken at all. The usual causes are a rule that got disabled, a trigger pointing at a list or label somebody renamed, or a Workspace that has burned through its monthly automation-run quota. The automation log tells you which one you’re dealing with, and checking it takes under a minute.
Read the automation log before you touch anything
Rebuilding a rule from scratch because it “isn’t firing” is the fastest way to waste an afternoon on this. Trello keeps two separate logs and the difference between them matters: one is scoped to a single automation, the other shows everything that ran on your behalf across every board you can see.
To open the log for one specific automation:
- Open the board, then open the board menu.
- Select Automation.
- Pick the tab that matches the automation type: Rules, Card button, Board button, Calendar, or Due Date.
- Select the Automation log icon next to the automation you’re investigating.
To see everything instead:
- Open any board, then open the board menu.
- Select Automation.
- Select Activity.
- Select the Activity log tab.
Both views are described in Atlassian’s automation log documentation, which also confirms the logs record trigger and action changes, not just runs. That detail is useful on shared boards: if a rule quietly started behaving differently, the log will usually show you when somebody edited it.
Interpreting what you see is straightforward. If the automation doesn’t appear in the log at all, it never fired — you have a trigger, permissions, or quota problem. If it appears with an error or warning, it fired and something downstream failed, which is a much narrower search.
Symptom to cause to fix
| What you see | Most likely cause | Where to fix it |
|---|---|---|
| Rule stopped firing on a specific date, board-wide | Workspace hit its monthly automation-run or operations quota | Automation → Activity → Workspace activity |
| Nothing in the log for that rule, ever | Automation is disabled on this board | Automation builder → enable/disable toggle |
| Log shows an error naming a list or label | Trigger or action target was renamed, archived, or deleted | Edit (pencil) the automation and re-select the target |
| Rule fires but only touches some cards | Per-run action cap, or a condition excluding the rest | Split the rule; review advanced trigger conditions |
| Scheduled or due-date rule runs at the wrong hour | Account time zone is out of sync | Automation time zone settings |
| Card button missing for teammates | Button is private, or not shared to the Workspace | Button sharing settings |
| Your rule vanished from a Premium Workspace board | An admin disabled it | Automation log (admin actions are recorded) |
Quota is the cause people rule out too early
This is the one that produces the classic “everything worked, then nothing worked, then on the first of the month everything worked again” pattern. Two things get metered, and they are not the same thing.
An automation run is counted every time an automation is triggered or a button is pressed. An operation is counted for every action the automation takes — at least one per action, and some actions such as sorting a list consume several. A rule with five actions therefore costs one run and a minimum of five operations each time it fires. Both are drawn from a pool shared across the Workspace.
| Per month | Free | Standard | Premium | Enterprise |
|---|---|---|---|---|
| Automation runs | 250 | 1,000 | Unlimited | Unlimited |
| Operations | 2,500 | 20,000 | 150,000 + 10,000 per user, capped at 250,000 | 150,000 + 10,000 per user, capped at 250,000 |
| Emails | 250 | 1,000 | 1,000 per paid user, capped at 100,000 | 1,000 per paid user, capped at 100,000 |
Those figures come from Atlassian’s automation quotas and limits page. A few things on that page deserve more attention than they get. Quotas reset on the first day of every month at midnight GMT — not on your billing date and not in your local time zone, which is why a team in Sydney or Los Angeles can see automations resume at an apparently random hour. A single automation run is capped at 20 total actions and operations on every plan, so a rule that fans out across a large list will stop partway rather than error loudly. And you can only have 20 card buttons and 20 board buttons enabled at once.
One myth worth killing: there is no carve-out for rules that only touch a single board or project. Atlassian’s documentation is explicit that quotas are pooled for all Workspace members on every plan, and that every trigger costs a run. If you have read otherwise, it was not from Atlassian. If quota is your ceiling, the honest options are consolidating rules so fewer of them fire on the same event, or moving up a tier — we break down what each Trello plan actually includes separately.
Check your own usage under Automation → Activity → Workspace activity, which shows runs and operations consumed this month alongside the Workspace name and the plan the quota is drawn from.
The rule is off, or it isn’t yours to control
Every automation in the builder has an enable/disable control that makes it active or inactive on that board. It is easy to toggle by accident and it produces exactly zero log entries, which is why it survives so much troubleshooting.
- Open the board menu, then select Automation.
- Find the automation under its type: Rule, Scheduled, Due Date, Card button, or Board button.
- Confirm the automation is enabled on this board.
- If it is enabled and still absent from the log, open the Edit (pencil) view and check the trigger before assuming the rule is at fault.
A wrinkle that surprises people on larger teams: on Premium Workspaces and Enterprise, admins have authority over other members’ automations. They can view and disable automations on boards in their organisation, and they can view and delete shared buttons — private buttons stay untouchable. Admin actions are written to the automation log, so if your rule disappeared, the log will name who did it. The Admin control itself only appears on the Rules and Calendar tabs.
Small annoyance worth naming: Atlassian’s own pages call the same tab “Calendar” in some places and “Scheduled” in others. They are the same thing.
Your trigger is aimed at something that no longer exists
Trello automations reference lists and labels the way a formula references a cell. Rename “In Progress” to “In progress” and any rule matching the old string quietly stops matching. Archive a list and rules that move cards into it have nowhere to put them. Nobody gets a warning, because from Trello’s point of view nothing illegal happened.
- Open the automation’s Edit (pencil) view.
- Re-select every list, label, and Custom Field named in the trigger and in each action, even the ones that look right.
- Save, then trigger the rule manually on a test card.
- Re-open the Automation log and confirm the run appears.
If your board naming changes often, referencing lists by position rather than by name is more durable. It is a documented option and it removes an entire category of breakage.
Conditions that can never all be true at once
Turning on the Advanced switch when selecting a trigger lets you stack multiple conditions on a rule or due-date trigger. Every condition must be true for the automation to fire. That is an AND, not an OR, and it is where most “my complex rule does nothing” reports end.
The practical test: strip the rule back to one condition, confirm it fires, then add conditions back one at a time. Two conditions that each look reasonable in isolation — a card being in a list it has already left, say, or a Custom Field that gets cleared by an earlier action in the same rule — can be mutually exclusive in practice. Ordering inside a multi-action rule matters more than the builder’s interface suggests.
Due-date and scheduled automations firing at the wrong hour
Trello automation detects your computer’s time zone and sets it as your account default. When those drift apart — you travelled, you changed a system setting, you set the rule up on a laptop in a different country — scheduled runs and the dates your rules write to cards go with the account setting, not the one you expect.
Atlassian’s guidance on setting the automation time zone includes a consequence worth reading before you click: updating your default time zone reschedules all of your Calendar automations to the new zone. If you are travelling temporarily, declining the prompt is usually the right call. If you have relocated, accept it once and expect a one-off shift in when your scheduled rules land.
Card buttons that never appear
Card buttons have four independent visibility settings, and getting one wrong produces a button that exists but nobody can see:
- Enabled by default — shows the button without anyone having to turn it on. Defaults to on; changeable at creation or later via the pencil icon.
- Show on this board — displays the button on all cards on this board, for you.
- Show on all Workspace visible boards — makes the button available on every Workspace board, but still only for you.
- Anyone in Workspace can enable this button — the one that actually shares it with other people.
The trap is the third setting. It reads like sharing and it is not. If a teammate says your button doesn’t exist, that combination is the first thing to check. And if a shared button appears on a private board, look at what it does before pressing it — a button written by someone else can move information off the board it sits on.
What happened to “Butler”
You will find tutorials online that describe writing Butler commands into cards on a list. That is the legacy Butler Bot, and it is no longer officially supported. Atlassian’s account is that Butler began as a bot (@butlerbot) that users added to boards and instructed through cards, was reworked into a Power-Up because the card-based interface interfered with boards and generated notifications for every subscriber, and was later integrated into Trello’s core interface as what the product now calls Automation.
Atlassian does not publish specific dates for those transitions in its current documentation, so treat any article giving you a precise acquisition or rebrand year with suspicion. What Atlassian does state plainly is that command runs are accounted for substantially differently between the old bot and core Automation, and that the legacy bot cannot use operations from Premium or Enterprise accounts. If you inherited a board still running bot-style commands, migrating them is not optional maintenance. For the wider picture of what else plugs into a board, see our guide to Trello Power-Ups.
Frequently asked questions
Does a rule that fires but does nothing still use quota?
Yes. Atlassian counts one automation run every time an automation is triggered or a button is pressed, regardless of outcome. Each action then costs at least one operation. A five-action rule consumes one run and a minimum of five operations per firing, which is why operations run out long before runs do.
Why did my automation only affect some of the cards?
Two documented caps apply. The total actions and operations in a single automation run is limited to 20 on every plan, and Trello also limits how many cards one run will affect — that second number is not published. Rules that sweep large lists should be split into smaller, narrower rules.
Can a Workspace admin disable my rules without telling me?
On Premium Workspaces and Enterprise, yes. Admins can view and disable other members’ automations on boards in their organisation, and can view and delete shared buttons, though not private ones. Every admin action is recorded in the automation log, so you can see exactly what changed and who changed it.
When exactly does my automation quota reset?
On the first day of every month at midnight GMT. It is not tied to your billing date and it does not follow your local time zone, so teams outside GMT will see automations resume mid-afternoon or mid-evening on the first. Worth knowing before you file a support ticket.
Is there a limit on how many automations I can create?
There is, though it is expressed oddly. Rather than a fixed count, Atlassian caps the total at 64,000 characters shared across all automations a single account creates — roughly 750 average-length automations by their own estimate. It is a database limit and cannot be raised. Most teams will never approach it.
If automation limits are shaping how you structure boards rather than the other way around, that is a signal worth taking seriously — either about how you’re running projects in Trello, or about whether the tool still fits. Our full Trello review covers where those ceilings start to bite.
Sponsored
