ClickUp Automations Not Working? Complete Troubleshooting Guide 2026

Why ClickUp Automations Stop Working (The Big Picture)

Before diving into specific errors, it helps to understand how ClickUp automations work under the hood. Every automation has three parts: a trigger (the event that starts it), optional conditions (filters that decide whether to proceed), and actions (what happens when triggered). Failures occur in all three layers, and the symptom you see on the surface doesn’t always tell you which layer is broken.

The second thing to know: ClickUp automations count against a monthly automation run limit based on your plan. If you hit the limit, all automations stop running until the month resets — and ClickUp doesn’t send you a prominent warning when this happens. This is the single most common cause of “my automations just stopped working” overnight.

Step 1: Check Your Automation Run Count First

Before troubleshooting individual automations, always check if you’ve hit your monthly run limit. In ClickUp, go to Settings → Automations (at the workspace level). At the top of the page you’ll see your current month’s automation usage: “X of Y runs used”. If this shows you’ve used 100% of your runs, all automations are paused until the next billing cycle.

If you’re hitting the limit regularly, you have three options: upgrade your plan for more runs, audit your automations to find inefficient ones consuming too many runs, or use ClickUp Brain AI to consolidate multiple simple automations into fewer, more targeted ones.

Problem 1: Automation Trigger Not Firing

Symptom: You perform the trigger action (change a status, move a task, add a due date) but the automation doesn’t execute. No errors appear anywhere.

Diagnostic Step: Check the Automation Activity Log

Every ClickUp automation has an activity log. Open the automation rule, and look for the “Activity” or “History” tab. This shows every time the trigger fired and what happened. If the log shows no recent activity after you triggered it, the trigger itself isn’t registering the event.

Common Cause 1: Wrong Space/Folder/List Scope

ClickUp automations have a scope — they only run on tasks within the Space, Folder, or List where the automation is configured. If you created the automation in “Space A” but are triggering it in “List B” inside “Space C”, it won’t fire. Fix: Open the automation settings and confirm the scope indicator at the top matches the location where you’re expecting it to run. If needed, recreate the automation at the correct level or add it to the specific List where you need it.

Common Cause 2: Trigger Conditions Are Too Restrictive

Many automation triggers include optional condition filters — for example, “When status changes to Done AND priority is Urgent”. If the task doesn’t meet ALL conditions, the trigger won’t fire. Fix: Edit the automation and review each condition. Remove conditions that might be filtering out legitimate trigger events. Test with a simple version of the rule first (no conditions), then add conditions back one at a time to identify which one is blocking it.

Common Cause 3: Automation Is Disabled

This sounds obvious, but it’s worth checking. In the automation list for your Space/Folder/List, look at the toggle on the right side of each automation. A grey/off toggle means the automation is paused. Fix: Click the toggle to enable it. Also check if there’s a workspace-level “pause all automations” setting that an admin may have enabled.

Problem 2: Trigger Fires But Action Doesn’t Execute

Symptom: The activity log shows the trigger fired, but the action (assign a user, change status, send notification) didn’t happen.

Common Cause 1: Permission Issue on the Action

The automation runs under the context of the user who created it (or the workspace bot, depending on your plan). If the automation tries to assign a task to a user who isn’t a member of the list, or move a task to a folder the automation “user” doesn’t have access to, the action silently fails.

Fix: Check the error in the Activity Log — it often specifies “User does not have permission” or “Target list not found”. For assignment actions, ensure the target user is a member of the list with at least Member-level access. For move actions, verify the destination list exists and is accessible.

Common Cause 2: External Integration Not Connected

If your automation action involves an external service (Slack, email, webhook, GitHub), the integration must be actively connected. If the connection was revoked, expired, or the app was removed from your workspace, the action fails silently.

Fix: Go to Settings → Integrations and check the status of the relevant integration. Reconnect or re-authorize it if needed. For Slack specifically: if your Slack workspace was migrated to a different plan or if someone removed the ClickUp app from Slack, you’ll need to re-add it from the Slack App Directory and re-authorize in ClickUp.

Common Cause 3: Automation Action Conflicts with Another Automation

If two automations are both triggered by the same event and their actions conflict (one sets status to “In Review”, another sets it to “Done”), the last one to execute wins — and the result may look like one of them isn’t working.

Fix: Review all automations in the same scope for overlapping triggers. Consolidate conflicting automations or add conditions to each one to ensure they’re mutually exclusive (e.g., “only run if assignee is X”).

Problem 3: Automation Runs Once Then Stops

Symptom: The automation works perfectly for the first few days, then stops firing. Or it fires once per task and then never again for the same task.

Common Cause: “Run Once Per Task” Setting

ClickUp automations have a setting that controls whether they can fire multiple times for the same task, or only once. If “Run only once per task” is enabled, the automation will fire the first time the trigger condition is met, then ignore future triggers for that same task.

Fix: Open the automation rule settings (the gear/settings icon within the automation). Look for a “Run once per task” or “Frequency” setting and change it to “Run every time conditions are met” if you want repeating execution.

Common Cause: Status Change Loops (Automation Creates Its Own Trigger)

This is a subtle but common problem. You create an automation: “When status changes to Done → assign to QA team”. But the assignment action itself triggers another automation that changes the status, which triggers the original automation again. ClickUp detects this loop after a few cycles and pauses the automation to prevent infinite execution.

Fix: Add a condition to your automation that prevents re-triggering. For example, add the condition “Only if assignee is NOT QA team” to the status-change trigger, so the automation won’t fire after the assignment was already made.

Problem 4: Slack Notifications from ClickUp Automations Not Arriving

Symptom: The ClickUp automation for Slack is enabled and the activity log shows it “ran successfully”, but the Slack message never arrives in the channel.

Diagnostic Steps

First, check the ClickUp activity log for the specific automation execution. If it shows “Success” on the Slack action, the message was sent from ClickUp’s side — the issue is on the Slack side. If it shows an error, note the error message and follow the integration reconnection steps above.

In Slack, check if the ClickUp app is still installed and active (Settings → Manage Apps → ClickUp). Also verify the channel specified in the automation still exists — if it was renamed or archived, the message is posting to a channel that no longer exists under that name.

Fix for “Success” but no message: Disconnect and reconnect the Slack integration in ClickUp Settings → Integrations → Slack. Then update the automation with the freshly authorized connection. This refreshes the OAuth token and usually resolves delivery failures.

Problem 5: Date-Based Trigger Not Firing on Schedule

Symptom: You have an automation set to fire “1 day before due date” or “on due date” but it’s not triggering at the expected time.

Common Cause: Time Zone Mismatch

ClickUp evaluates date triggers based on the workspace time zone, not the individual user’s time zone. If the workspace is set to UTC but your team works in EST (UTC-5), a trigger set for “due date” fires at midnight UTC — which is 7pm the previous day in EST. Tasks may appear to trigger “early” or “late” depending on the gap.

Fix: Go to Settings → Workspace Settings → Time Zone and set it to your team’s primary working time zone. All date-based automations will then evaluate times in that zone.

Common Cause: Task Has No Due Date or Due Date Was Changed

If a task’s due date is removed after the automation trigger was registered, the scheduled execution gets cancelled. Similarly, if the due date is changed to a past date after an automation already “missed” it, the trigger won’t retroactively fire.

Fix: Ensure tasks have due dates set before the trigger window. If a due date changes, ClickUp re-evaluates the trigger — but only for future dates, not past ones.

Problem 6: Automation Works in Testing But Fails in Production

Symptom: When you manually click “Run” to test an automation rule, it works. But when the real trigger fires, it doesn’t execute correctly.

Cause: Manual test runs execute the automation in a slightly different context — they run immediately, bypass some condition checks, and may use the admin user’s permissions rather than the automation bot’s permissions. Conditions that fail in production often pass in test mode because of these differences.

Fix: Don’t rely solely on manual test runs. Create a test task that exactly replicates your real conditions — same list, same status, same assignee, same custom field values. Trigger it naturally (by changing the status manually, for example) and watch the activity log for that specific execution. This gives you a true production test.

Advanced: Using ClickUp Brain AI to Diagnose Automation Issues

In 2026, ClickUp Brain (available on Business plan and above) can help diagnose automation problems. In the ClickUp AI chat, you can ask questions like “Why isn’t my automation firing for tasks in [List name]?” or “Show me all automations that trigger on status change to Done”. Brain can surface automation conflicts, suggest simplifications, and even write new automation logic for you.

For complex multi-step automations, Brain can also help you break them into simpler, more reliable sequences — which often fixes mysterious failures that occur because a chain of actions becomes too complex for a single automation to handle reliably.

When to Contact ClickUp Support

If you’ve gone through the entire checklist above and automations still aren’t working, it’s time to contact ClickUp support. Before reaching out, collect: the specific automation ID (found in the URL when editing the automation), screenshots of the activity log showing the failure, your workspace plan, and the exact trigger/action sequence. ClickUp support can access server-side logs that aren’t visible to users, which often reveals edge-case failures that don’t appear in the activity log.

Known issues are tracked in the ClickUp status page (clickup.com/status) — check there first to see if there’s an ongoing incident affecting automations broadly.

Frequently Asked Questions