Most monday.com automations stop working for one of a handful of documented reasons: the owner was deactivated, a column or board the recipe points at was deleted, the account burned through its monthly action quota, or two automations sharing a trigger are cancelling each other out. Run history tells you which.
The frustrating part is that monday.com does not always warn you. Some deactivation scenarios send no notification at all, and the error only ever appears on the board’s Automations page. An automation can sit switched off for three weeks while a project manager wonders why nobody is being assigned anything.
Check Run history before you touch the recipe
The instinct when an automation misbehaves is to open it, poke at the blocks and rebuild it. Resist that. Rebuilding destroys the evidence, and if the cause is an account-level limit or a permission change, the rebuilt automation will fail in exactly the same way. Read the log first.
- Open the board and click Automate at the top of the board.
- Click the Manage tab.
- Click Run history.
- Scan the list for the run in question. Each row is marked In progress, Failure, or successful.
- Click the downward arrow at the right of the row to expand it. Failed runs display a suggested fix highlighted in red directly under the entry.
- Hover the cog icon on the row to see how many actions that single run consumed. This is the number that matters when you are close to a quota.
Two limitations worth knowing before you start hunting. Run history only retains the past 10 days of data, so a failure from last month is simply gone. And if you need to trace one specific item rather than the whole board, open the item, click Activity Log, then Automation activity — that gives you the automation view for that item alone. The board activity log also carries an automation avatar next to any change made by a recipe; clicking it jumps you straight to the automation responsible, which is the fastest way to find the culprit when a status keeps flipping and nobody will admit to it.
Symptom to cause, at a glance
| What you are seeing | Most likely cause | Where to fix it |
|---|---|---|
| Automation toggle is off and nobody turned it off | Owner deactivated, or a target column/board was deleted | Board Automations page — read the red error text |
| Some runs succeed, some fail, same recipe | Competing automations on the same trigger | Merge into one custom automation |
| Everything stopped on the same day across all boards | Monthly action quota exhausted | Autopilot hub > Usage |
| Automation fails only during bulk edits or imports | Per-minute rate limit | Toggle back on, then stagger the trigger volume |
| Run history is empty for the item entirely | The trigger never fired | Recipe conditions and how the value was changed |
| You cannot create or edit automations at all | Quota fully consumed, or you are a viewer | Admin > Usage stats, or your user role |
The owner was deactivated, so the automation went with them
This is the single most common cause in accounts with any staff turnover, and it is the one that catches people out because the automation looks fine to everyone else. Automations belong to the person who built them. Deactivate that person and their recipes stop, account-wide. The error on the board Automations page reads: “The automation owner was deactivated from your account.”
There is a related version of the same problem. If the creator is still active but has been unsubscribed from a permissions-enabled board, had their editing rights revoked on a column used in the recipe, or been changed from member to viewer, you get a different message: “The user who created this automation doesn’t have permissions to make changes on this board.” Viewers cannot create or edit automations at all, so a well-meaning licence downgrade will silently kill a department’s workflow. monday.com lists all of these scenarios in its guide to deactivated automations.
The durable fix is to move ownership rather than reactivate a leaver:
- Reactivate the departed user temporarily — ownership cannot be transferred from an inactive account.
- Click your profile picture, then Administration.
- Click Directory in the left pane.
- Click Automations ownership.
- Select the departing user in the first dropdown and the new owner in the second.
- Click Transfer ownership. The automations reactivate once the transfer completes.
Set the account-level fallback too, or this repeats with the next leaver: in the same area, open Keep automations running when users are deactivated, pick a default owner from the dropdown, and click Save changes. Use a genuine admin who is not going anywhere, not a shared inbox.
Two automations, one trigger, one loser
This produces the worst kind of bug — intermittent, item-specific, impossible to reproduce on demand. monday.com calls them competing automations: two recipes with the same trigger whose actions conflict when they run simultaneously. The textbook case is one automation that archives an item when status changes to Done and a second that sets another status column on the same trigger. Both fire together, and the second fails because the item it is writing to has just been archived out from under it. Neither recipe is wrong on its own, which is why people spend an afternoon rebuilding both.
monday.com’s official fix for competing automations is to consolidate rather than reorder:
- Open the board Automations page and identify every recipe sharing the same trigger.
- Delete the competing recipes.
- Build a single custom automation containing all of the required actions in sequence.
- Place any final-stage action — move item to board, archive item, or delete item — as the last step, after every action that still needs to read or write the item.
If you are new to building multi-action recipes, our guide to building monday.com automations covers the custom automation builder in more depth. The same ordering rule applies to subitem automations, where deleting or moving a parent mid-sequence causes identical failures.
You have not run out of automations, you have run out of actions
Two facts trip people up here. First, automations and integrations are not available on Free or Basic at all — they start at Standard. Second, the quota is measured in actions, not in automation runs, and one run can consume several actions.
| Plan | Automation actions per month | Integration actions per month |
|---|---|---|
| Free | Not available | Not available |
| Basic | Not available | Not available |
| Standard | 250 | 250 |
| Pro | 25,000 | 25,000 |
| Enterprise | 250,000 | 250,000 |
The gap between Standard and Pro is a hundredfold, which tells you what monday.com thinks of 250 actions. Here is where it goes, per the actions and limits documentation: a recipe that creates an item and maps Status, Tag, People or Dropdown columns burns one action per mapped column plus one for creating the item. A recipe that notifies board subscribers burns one action per subscriber — six subscribers, six actions, every single time it fires. Condition steps in the workflow builder consume actions too. And apps installed from the marketplace can generate their own automations that quietly eat the quota in the background.
When you hit 100%, you get a 72-hour grace period before runs are paused. Overage does not vanish — the excess is deducted from the following month’s allocation, and it is entirely possible to start a month with zero actions available. Once the quota is fully consumed the account is also blocked from editing or adding automations, which is a genuinely nasty failure mode: you cannot fix the runaway recipe that caused the problem.
To check where you stand, open the Autopilot hub and click the Usage tab, or go to Administration > Usage stats for a breakdown by top automations, boards and creators. Note that the reset date depends on how you pay — monthly plans refresh on the same day of the month you activated, annual plans refresh on the 2nd day of every month.
One honest caveat: monday.com’s two relevant articles disagree on warning thresholds. The actions and limits page describes alerts at 50% and 80%; the automations pricing page describes emails at 50%, 75% and 100%. Do not rely on either. Check usage manually before a busy month. If the numbers push you toward an upgrade, compare the tiers against current monday.com plan pricing before committing, because the per-seat cost changes more often than the action allowances do.
Separately, the monthly action limit and the active workflow limit are two different ceilings. Hitting one does not affect the other, so “I still have actions left” does not explain why a new workflow builder recipe will not activate.
Deleted columns, groups and boards
If a recipe depends on a group, column, subitem, board or workspace that someone deleted, it deactivates the next time it is triggered. For a deleted board the error is explicit: “The selected board no longer exists.” Cross-board recipes are the most exposed, because the board being deleted is usually not the board you are looking at.
- Open the trash section for the relevant workspace. Deleted elements are retained for 30 days.
- Find the deleted board, column or group, click the three dot menu and click Restore.
- If it is past 30 days or the deletion was deliberate, open the automation from the notification instead and point it at a replacement target.
- Toggle the automation back to On — restoring the target does not reactivate it for you.
Watch for the item limit as a variant of the same problem. If a recipe tries to create an item on a board that has hit its item limit, the run will not complete; it retries the following minute and the automation is deactivated if the condition persists. Archive or delete items to clear headroom, then switch it back on.
Rate limits: too many triggers in a single minute
Separate from the monthly quota, each automation or integration template can only perform so many triggers and actions per minute. Exceed it and that template is disabled with an error on the board Automations page.
Three things reliably trip it: an automation loop, API or webhook traffic firing recipes in bursts, and batch actions applied across a large selection of items. monday.com warns you when you build something that will loop, but it lets you create it anyway, so the warning gets clicked past.
Toggling the template back on restores it, but that is a symptom fix — find out what caused the burst. If a bulk status change across 400 items is routine for you, the process needs restructuring, not the automation. Integration rate limits are set by the third-party service’s API rather than by monday.com, so an Outlook or Gmail recipe failing under load is being throttled at the other end. Moving that step to a Zapier integration with monday.com sometimes gives better retry behaviour, though it adds a moving part.
When Run history shows nothing at all
Everything above assumes a run that failed. If Run history has no entry for the item, the automation did not fail — it never fired. monday.com does not document this as a failure category, so there is no error message to read and no red suggestion to follow. Work through it manually:
- Confirm the trigger column is the exact column the recipe references, not a similarly named duplicate. Boards accumulate these.
- Check whether the status was set to the specific label the recipe watches for, rather than any change to the column.
- Check whether the change was made on a subitem while the recipe watches the parent, or the reverse.
- Check whether the value was written by another automation. Some triggers respond to a person changing a value, not to a system-set value.
- Change the value manually yourself and watch Run history. If a manual change fires it and the automated path does not, the problem is upstream, not in this recipe.
If the automation is firing correctly but people are simply not hearing about it, that is a different problem — see our fix for when monday.com notifications are not arriving.
Frequently asked questions
Why did my monday.com automation turn itself off?
monday.com deactivates automations for eight documented reasons: the owner was deactivated, the owner lost board or column permissions, a template assignee lost access, a target group, column, subitem, board or workspace was deleted, the item limit was reached, the per-minute rate limit was hit, or the whole account was inactive for two or more weeks.
How far back does Run history go?
Ten days. monday.com’s Run history feature retains only the past 10 days of automation activity, on the board view and on individual items. Anything older is unavailable, including through support. If an automation fails intermittently, check the log within a week rather than waiting to gather more examples first.
Does one automation run always use one action?
No. Mapping a Status, Tag, People or Dropdown column into a created item costs one action each, plus one for the item itself. Notifying board subscribers costs one action per subscriber. Workflow builder condition steps consume actions as well. A single recipe can easily cost five actions per run.
Why can’t I create or edit automations at all?
Two likely reasons. Your account has consumed its full monthly action allocation, which blocks editing and adding automations until the cycle resets or you upgrade. Or your user role is viewer — viewers cannot create or edit automations. Ask an admin to check usage stats first, then your role.
Will rebuilding the automation fix it?
Sometimes, but it is the wrong first step. Rebuilding fixes a corrupted recipe and nothing else. If the cause is a deactivated owner, an exhausted action quota, a deleted target board or a competing automation on the same trigger, the rebuilt version fails identically — and you have lost the original configuration.
Sponsored
