Trello Butler Not Working? Complete Fix Guide for Trello Automation Issues in 2026
- Trello Butler automation failures fall into five predictable categories: monthly run limit exhaustion, permission gaps, renamed or deleted trigger targets, complex condition logic errors, and the legacy Butler Bot vs.
- modern Automation naming confusion.
- This guide covers every failure mode with the diagnostic steps and actual fixes — not just “contact support.”
- Butler Bot vs. Trello Automation: The Naming Confusion
- Issue 1: Monthly Automation Run Limits
- Issue 2: The Rule Is Disabled
- Issue 3: Trigger Target Renamed or Deleted
- Issue 4: Permission Requirements
- Issue 5: Complex Conditions That Never Evaluate True
- Issue 6: Due Date Automations at the Wrong Time
- Issue 7: Use the Automation Log
- Issue 8: Card Button Automations Not Appearing
- Frequently Asked Questions
Butler Bot vs. Trello Automation: The Naming Confusion
“Butler” was originally a third-party Power-Up acquired by Atlassian in 2018, then integrated natively, then rebranded in 2021 as simply “Automation.” Search results for “Trello Butler not working” return documentation from three different eras — some describing a UI that no longer exists. Modern Trello Automation is accessed from the board’s top navigation bar under “Automation” — no Power-Up required. Any guide referencing “opening the Butler Power-Up” is outdated.
Issue 1: Monthly Automation Run Limits
Trello’s automation limits are lower than most users realize: Free workspaces get 250 command runs/month across all boards, Standard gets 1,000/month, Premium is unlimited. Each action within an automation counts as one run — a rule with 4 actions counts 4 runs per trigger. When limits are hit, automations don’t error — they simply stop executing. The rule appears active and enabled with no signal to board members.
Check and Manage Run Usage
- Go to Automation (board top nav) → “Usage” tab — shows current month’s runs used vs. limit
- Workspace admins: Workspace Settings → Automation Usage for aggregate view across all boards
- Limits reset on the first day of each calendar month — waiting is the free solution near month-end
- Reduce consumption: replace “When any card moves” triggers with specific list-to-list triggers — this alone cuts run count by 70-80% on active boards
Issue 2: The Rule Is Disabled
Each automation rule has an individual enable/disable toggle in the Automation center. Rules can be accidentally disabled during editing — Trello sometimes disables a rule during an edit session and requires you to manually re-enable it. Also check: rules created by a board member who has since left the workspace may be disabled if their account was downgraded or removed. Check the toggle state before any other diagnosis.
Issue 3: Trigger Target Renamed or Deleted
The most common cause of “was working, now stopped.” A rule configured for “When a card is moved to [List Name]” breaks if that list is renamed or deleted. Same for labels, members, and custom fields. Trello doesn’t alert you when a referenced element changes — the rule continues to appear active, attempts to trigger, and fails silently when the action target doesn’t match any existing board element. Always audit all rules immediately after renaming any list or label.
Issue 4: Permission Requirements
Creating automation rules requires board membership — observers cannot create automations. Actions that affect board settings (archiving cards, changing board visibility, moving cards between boards) require board admin rights. Cross-board automations require the automation creator to be a member of the destination board. If the creator was removed from a destination board after setup, the cross-board transfer action will fail without any error visible on the source board.
Issue 5: Complex Conditions That Never Evaluate True
Rules with multiple AND conditions can fail to trigger because the combined condition logic is never simultaneously true. “When a card is moved to Done AND the card has label ‘Approved’ AND the card has a due date in the past” will never fire if cards are moved to Done before their due date. Diagnose by removing all but one condition and testing. If it fires, re-add conditions one at a time to identify which condition prevents execution, then adjust the logic.
Issue 6: Due Date Automations at the Wrong Time
Due date triggers fire based on UTC time, not your local timezone. “When a card’s due date arrives” means midnight UTC on the due date. For users in UTC+5:30, this fires 5.5 hours early in local time. Account for your timezone offset when setting due dates for automation triggers. It’s inelegant, but it’s the only way to control timing until Trello adds timezone support for due date triggers.
Issue 7: Use the Automation Log
Most users never open the Automation log — it’s the single most useful debugging tool. From Automation → click “Log” in the automation center navigation. The log shows: trigger timestamps, which rule fired, which actions were attempted, and any error messages from failed actions. Zero log entries means the trigger condition has never been met (problem is your trigger logic). Log entries with errors mean the trigger works but the action fails (problem is the action’s target or permissions).
Issue 8: Card Button Automations Not Appearing
Card buttons created in Automation should appear on every card’s back. If they’re not appearing: (1) verify the button was created with “This board” scope (not “All boards” inadvertently) — if created for “this board” it only appears on cards in that board, (2) you must be logged in as a board member — non-members and observers don’t see card buttons, (3) try a hard refresh — card buttons sometimes require a full page reload to display after creation.
📚 Related Reading on WorkManagement Hub
🔗 Official Resources
Frequently Asked Questions
No hard limit on rules per board. The constraint is monthly run consumption — each action execution counts against your workspace’s monthly limit (250 Free, 1,000 Standard, unlimited Premium). You can have 50 rules that rarely trigger or 5 rules that collectively hit the limit mid-month.
Yes. Cross-board card moves are supported. The automation creator must be a member of both source and destination boards. If permissions change after setup, cross-board actions will fail silently.
Intermittent firing usually means the trigger condition is only sometimes met. Review your rule’s condition logic — all AND conditions must be simultaneously true. Also check whether you’re approaching your monthly run limit, which causes some triggers to execute but not others as the limit is hit.
Yes — “Butler” was the historical name for Trello’s automation when it was a separate Power-Up. Atlassian rebranded it as “Automation” and built it natively into every Trello board. Same engine, different name and location. Any guide referring to “Butler” is describing the same feature as modern “Automation.”
Not directly via the UI. Workaround: copy the board (including automations) as a template, use the copy as the basis for new boards. Trello has no “export/import automations” feature yet.
🎯 Expert Bottom Line
Trello Butler failures are diagnosable in under 5 minutes with the right sequence: check the automation log, verify run limit usage, confirm the toggle is enabled, then inspect whether referenced lists/labels still exist with the same names. The monthly run limit is the most disruptive failure because it’s invisible — build awareness of your workspace’s monthly consumption and audit high-frequency triggers to stay under the threshold. For teams hitting limits consistently, Standard plan’s 1,000 runs/month is often the right upgrade, and consolidating multi-action rules reduces run consumption immediately.
