Your ClickUp Automation Stopped Running. Here Is Why.
- Branden Bell
- Aug 12
- 6 min read
Your ClickUp automation worked for months. Then it quietly stopped, and nobody noticed until a client asked why they never got their kickoff task.
Here is the part most people miss. ClickUp does not always tell you when an automation breaks. Sometimes it turns the automation off on purpose, sends one email to one person, and moves on.
I am a PMP and a ClickUp Verified Consultant. I rebuild workspaces for travel advisors, agencies, and service businesses, and a dead automation is one of the most common things I find on the first day of a rebuild. Almost none of them were ever reported. They stopped, and the team quietly went back to doing that step by hand.
Start with the Activity tab, not the rule
Do not open the automation and start editing. Open the record of what it actually did.
Click your Workspace avatar in the upper-left corner, select Automations, then select the Activity tab. It is filtered to your current location by default, so switch the location filter if the rule lives somewhere else.
Every run shows the time it ran, the automation name, the location, the task that triggered it, who triggered it, and a status. You can filter by location, date run, and status.
Four statuses tell you almost everything:
Success: the automation completed its actions.
Failed: one or more steps did not complete. If a single step fails, the entire run fails.
Skipped: the criteria required were not available, so it did not act.
Pending: it is still attempting to finish the job.
Skipped is the one people misread. A skipped run is not a bug. It means the automation fired and found nothing to do, which usually means your trigger is right and your conditions are wrong.
A failed run and a skipped run point at completely different problems. Reading the status wrong is how people rebuild a rule that was never broken.
ClickUp deactivates automations that keep failing
This is the mechanic almost nobody knows about.
If the same automation fails more than five times in one week with the same error, ClickUp deactivates it. That is deliberate. The stated reason is to stop a broken rule from burning through your monthly action budget.
Then it emails the person who created it. If that person is no longer part of the Workspace, the email goes to the Workspace owner instead.
Email and Custom Field errors get harsher treatment. ClickUp emails immediately, deactivates the automation, and tests it.
So the question to ask about a missing rule is not what did I change. It is: who built this, do they still work here, and did anyone read that email.
Deactivated automations do not disappear. In the Automations modal, open the Manage tab and switch from Active to Inactive to find them. The off and on toggle sits in the upper-right corner of each one.
Your evidence expires, and faster than you expect
Here is the constraint that should decide how you troubleshoot.
ClickUp stores your automations usage history for a limited window, and on most plans that window is tiny:
Free Forever, Unlimited and Business: 1 day of activity.
Business Plus: 30 days of activity.
Enterprise: 6 months of activity.
Read that first line again. If you are on Business, which is where most of the agencies I work with sit, you get one day. Notice on Thursday that something stopped on Monday and the run history that would have explained it is already gone.
That changes the order of operations. Check Activity first, capture what you see, then start theorising.
On most plans the record of what your automation did survives about a day. Diagnose first, discuss later.
Six checks before you rebuild the rule
ClickUp publishes its own troubleshooting list, and it is better than most of what gets written about this. When one specific automation is not working, check:
Is the automation still active: see the deactivation rule above.
Did the task or event meet the trigger criteria: triggers are literal, and you only get one per automation.
Is another automation running at the List, Folder or Space level: two rules touching the same task is the most common cause I find on a rebuild.
Did you exceed your monthly usage limit: covered in the next section.
For task created automations that set a status: does that status exist in the destination.
For task created automations that set an assignee: does that person have access to the automation location.
Two more that catch people out. There is no order of execution based on hierarchy, so a Space automation does not run before a Folder automation in that Space. There is no order based on which one you created first either. Actions inside a single automation do run in the order you placed them.
If you need one rule to run after another, make the first automation action the trigger for the second. That is the supported way to sequence them.
And when an automation creates a task or List that comes out missing information, check that the same ClickApps are enabled in both locations. A Custom Field that does not exist in the destination cannot be filled.
When nothing failed and nothing ran
Sometimes the Activity tab is simply empty. That usually means the whole Workspace is paused.
Automation actions are metered monthly, and when your limit is exceeded, the automations in your Workspace are paused for the rest of that month. Limits reset on the first of every month, Pacific Time. I broke down how those action budgets differ by plan in my guide to which ClickUp plan you actually need.
Owners and admins get an alert email at 90 percent of the monthly limit and again once usage passes 100 percent. Members do not. If your admin is not the person watching the workspace day to day, that email lands somewhere nobody reads.
You can check the number yourself. From a Space, Folder or List, click the Automate button, then Manage Automations, then the Usage tab. One caveat before you trust it: the usage tab updates every ten automation uses, so it is close to live but not exact.
Two other reasons for total silence. Guests cannot create automations at all. And if nobody can see the Automate button, a Workspace owner or admin has not enabled the Automations ClickApp yet.
Build rules that do not break in the first place
Most of the dead automations I find were fragile the day they were built.
The official recommendation is to create the simplest automation you can, and the hard limits back that up: one trigger, up to fifteen conditions, and up to six actions in a single automation.
Three habits that keep them alive:
Name and describe every automation: you can add a description in the Manage tab, and it is the difference between a rule your team can audit and a rule nobody dares touch.
Keep one rule per outcome: stacking six actions into one automation means a single failed step kills all six.
Open the Inactive tab once a month: it takes two minutes, and it is where broken rules go to sit quietly.
On the client onboarding workflows I build, the automation that matters most is almost always the one that creates the client task set. That is the one worth checking on a schedule, because when it fails silently, the first person to notice is the client.
When it is worth bringing someone in
If one rule broke, fix the rule. Nothing on this page needs a consultant.
If you open the Manage tab and find twenty automations, half of them inactive, and nobody in the room can explain what six of them were for, that is not a troubleshooting job. That is a workspace with no owner.
For a solo operator or a small team running one repeatable delivery path, ClickUp Build in a Day is the focused version: a tailored hierarchy and one delivery Space, up to five custom fields, up to three automations, a CEO dashboard, an AI Super Agent, and a screen recorded walkthrough. It runs on three virtual meetings that each take about an hour of your day, so it is a real commitment while it is happening.
When the sprawl runs across teams and the whole client delivery needs rebuilding with the team trained on it, that is the ClickUp Client Delivery OS: a 30 day engagement, up to 80 hours of expert build time, SOPs, hands on training, and support through all 30 days.
Not sure which end of that you are on? Start with the questions in my guide to hiring a ClickUp expert, then book a call.
Sources
An automation that fails loudly is a small problem. One that fails quietly is an invoice you never sent. If you want yours audited properly, book a free call and we will go through them together.
Comments