Automation Not Triggering?
Here’s Why It Happens
The interactive guide to diagnosing and fixing the 10 most common monday.com automation failures—from first-time admins to complex cross-board setups.
Jump to section
How monday.com automations actually work
Before you can diagnose what’s broken, you need one key mental model: automations are event-driven, not always-on monitoring.
Trigger
The specific event that starts the automation. Not a state — a change.
Condition
What must be true at the moment the trigger fires. Evaluated once, not continuously.
Action
What the automation actually does—only if the trigger and conditions both match.
If a status field is set at item creation (e.g. from a form), the “when status changes to X” trigger will never fire—because nothing changed. The trigger is the change event, not the value being present.
If you create a new automation and expect it to catch items that already meet the condition, it won’t. The trigger event must happen after the automation is active.
🔍 Diagnose my automation issue
Answer 3 quick questions to narrow down the most likely cause for your specific situation.
🎯 Most likely cause: Form-created items bypass “status changes” triggers
When an item is created via a form with a status already set, no “change” event fires — so your “when status changes to X” automation never runs. This is one of the most common trip-ups.
→ See Cause #7 below for a full breakdown.
🎯 Most likely cause: Moving an item ≠ creating an item
monday.com explicitly documents that moving an item to a board does not fire “item created” triggers on the receiving board. If your automation is on Board B expecting newly created items, items moved from Board A won’t trigger it.
→ See Cause #8 below for the full explanation.
🎯 Most likely cause: Trigger and condition are in the wrong order
If your automation fires “when Status changes to X, and only if Budget is filled” — but users fill Budget after setting the status — the condition check happens at the moment of the trigger and comes back false.
→ See Cause #1 below for examples.
🎯 Most likely cause: Automation was deactivated by the platform
monday.com automatically deactivates automations when their referenced targets (groups, boards, statuses) are deleted, or when rate/item limits are hit. This is silent — you won’t get an alert unless you check the Automations center.
→ See Cause #2 and Cause #6 below.
🎯 Most likely cause: Creator lost access (unauthorized user error)
Automations run under the permissions of the person who created them. If that person was removed from the board, changed to a Viewer role, or left the team, the automation can fail with an “unauthorized user” error — often silently.
→ See Cause #9 and Checklist Step #5 below.
🎯 Most likely cause: Monthly automation action limit reached
monday.com plans cap monthly automation actions. When the account hits its limit, automations don’t queue up — they just stop. This often looks like a random failure because it hits mid-month with no warning in-app.
→ See Cause #3 below.
🎯 Most likely cause: Competing automations or a logic loop
When two or more automations act on the same item or columns, they can conflict, overwrite each other’s output, or trigger each other in a loop. monday.com’s loop detection can suppress automations that create circular chains.
→ See Cause #10 below.
🎯 Most likely cause: Per-minute rate limit during bulk operations
Separately from monthly limits, monday.com enforces per-minute rate limits on automation triggers. Bulk imports or API pushes that create/update thousands of items at once can exceed this and cause throttling or temporary deactivation.
→ See Cause #4 below.
🎯 Most likely cause: Unsupported column type in the recipe
Not all column types work as automation triggers or conditions. Some are simply unsupported in certain recipe contexts, and cross-board column mapping has its own restrictions. This often appears as “the option doesn’t exist” or the automation silently skips those items.
→ See Cause #5 below.
The 10 most common root causes
Click any cause to expand the root cause, a real-world example, and a concrete fix.
Automations evaluate conditions at the exact moment the trigger event fires. If users perform steps in a different order than you expected—like filling in a required field after setting the status—the condition check may fail every time.
monday.com automatically deactivates automations when a referenced target (group, board, status label, user) is deleted, or when rate/item limits are exceeded. You won’t receive an alert—you have to check the Automations center.
Every monday.com plan includes a monthly cap on automation actions. When that limit is hit, automations stop executing—they don’t queue or retry. This can feel like a random failure because it often happens mid-month.
Beyond monthly limits, monday.com also enforces per-minute rate limits. Large imports, API pushes, or bulk updates that fire hundreds of automations in seconds can cause throttling or temporary deactivation.
Not all column types work as automation triggers or conditions. Some are simply unsupported in certain recipe contexts—they either don’t appear as options or the recipe silently skips those items.
Renaming a status label is usually safe (the underlying index stays stable). But deleting and recreating labels resets their indexes, which can break existing automation recipes that referenced the old label.
monday.com “change” triggers are designed to catch user edits. When an update comes from a form submission (pre-set field), another automation, or an API write, it may not register the same way—and the trigger doesn’t fire.
Automations are board-scoped. They only trigger off events on the board where they live. Moving an item to another board is not considered creating a new item—so “item created” triggers on the receiving board won’t fire.
Automations and integrations run under the permissions of the user who created them. If that user left the team, was removed from a private board, or had their role changed to Viewer, the automation can fail with an “unauthorized user” error—usually silently.
When two or more automations touch the same columns or items in rapid sequence, they can conflict, overwrite each other’s output, or trigger each other in an endless loop. monday.com’s loop detection may suppress some automations entirely.
✅ Step-by-step troubleshooting checklist
Work through this in order. Each step separates a different category of failure. Click each step as you complete it.
Automation Troubleshooting Checklist
🎉 Checklist complete!
You’ve covered all nine diagnostic steps. Still not resolved? It may be a structural architecture issue — see the section below about when to bring in an expert.
Build automations that stay reliable
Most recurring failures are architecture issues. These practices prevent them at the source.
Standardize statuses as a governed system
Define “stage gate” statuses that are the only ones allowed to trigger critical routing. Rename labels thoughtfully — never delete and recreate without an automation audit.
One decisive trigger per workflow stage
Avoid chaining 3+ automations that each fire on status flips. Every extra link is a race condition waiting to happen. Consolidate into a single, final trigger for each stage gate.
Cross-board: events on A, actions on B
Treat cross-board workflows as “events on Board A cause actions on Board B” — not as “Board B will react as if items were created there.” Moving ≠ creating.
Monitor with Run History, not intuition
Run History is operational instrumentation. Use it weekly on critical automations to confirm what triggered, what failed, and which automation made a change — before users notice a problem.
Design for volume
High-volume teams should treat monthly action limits and per-minute rate limits as hard architectural constraints — not edge cases. Audit action usage quarterly.
Audit duplicated boards immediately
Board duplications can silently drop or distort automation recipes. Never assume a duplicated board’s automations are complete and correct — always do a post-duplication audit.
When it’s time to bring in an expert
If you’ve checked triggers, logs, and permissions — and automations still aren’t reliable — the issue is usually structural.
Too many competing rules — cross-board routing built on wrong trigger types — mirror/subitem limitations creating hidden data gaps — or volume pushing your account into rate limit behaviors. These don’t get fixed by reconfiguring individual automations.
Structural automation failures compound over time — more boards, more rules, more conflicts. A one-time review of governance (statuses & permissions), board architecture, and volume-aware patterns typically resolves months of recurring issues.
Still stuck? FlowFam can fix it.
We help teams repair and redesign monday.com systems so automations run reliably at scale — through governance, board architecture, and performance-aware automation patterns that don’t collapse under pressure.
