What causes "Asana Rules Not Working or Stuck in Processing"?

Trigger conditions don't match what actually happens (wrong section, field or project) Another rule conflicts or overrides it Rules don't fire from actions taken by other rules Rule owner lost access to the project or tasks Integration-based actions need the app connected (e.g. Google Workspace for email) Asana-side incidents (Aug 2026 rules stuck in Processing; Sep 21, 2026 EU automations outage) Execution delays

How do I fix "Asana Rules Not Working or Stuck in Processing"?

1. Check the status page: Look for automation or rules incidents on Asana's status page If one is active, wait - rules may run late once the backlog clears 2. Read the rule's run history: Open the project > Customize > Rules Open the rule and check its recent runs and error messages 3. Re-check trigger and scope: Confirm the trigger (e.g. task moved to section) matches how people actually work For My Tasks rules, check you edited the right rule 4. Avoid chaining rules: Rules don't trigger from other rules' actions Combine the steps into a single rule with multiple actions 5. Fix rule owner permissions: Make sure the rule creator still has access to the project and target tasks Recreate the rule under an account that has access if needed 6. Reconnect required apps: For actions using integrations (e.g. sending email), connect the relevant app such as Google Workspace 7. Send rule IDs to support: If rules are stuck in Processing, contact support with rule IDs, a task link and a screen recording - staff asked for these during the 2026 incident

Try or Bye

Browse all analyzed products with real user feedback patterns.

Asana Rules Not Working or Stuck in Processing

Ongoing Web Updated October 21, 2026

Quick answer

Asana rules fail because of mismatched triggers or scope, conflicting rules, rules that rely on other rules, rule owners losing access, or Asana-side incidents like the August 2026 'Processing' issue. Check the rule's run history first.

Most likely fix: Check the status page.

Symptoms

A rule shows as active but never runs, runs in some projects but not others, shows 'Processing' or 'Running' indefinitely, or its history says it could not act because the rule owner lacks access.

Why it happens

Trigger conditions don't match what actually happens (wrong section, field or project)
Another rule conflicts or overrides it
Rules don't fire from actions taken by other rules
Rule owner lost access to the project or tasks
Integration-based actions need the app connected (e.g. Google Workspace for email)
Asana-side incidents (Aug 2026 rules stuck in Processing; Sep 21, 2026 EU automations outage)
Execution delays

How to fix it

Try these in order — the most common fix is first.

1. Check the status page
1. Look for automation or rules incidents on Asana's status page
2. If one is active, wait - rules may run late once the backlog clears
2. Read the rule's run history
1. Open the project > Customize > Rules
2. Open the rule and check its recent runs and error messages
3. Re-check trigger and scope
1. Confirm the trigger (e.g. task moved to section) matches how people actually work
2. For My Tasks rules, check you edited the right rule
4. Avoid chaining rules
1. Rules don't trigger from other rules' actions
2. Combine the steps into a single rule with multiple actions
5. Fix rule owner permissions
1. Make sure the rule creator still has access to the project and target tasks
2. Recreate the rule under an account that has access if needed
6. Reconnect required apps
1. For actions using integrations (e.g. sending email), connect the relevant app such as Google Workspace
7. Send rule IDs to support
1. If rules are stuck in Processing, contact support with rule IDs, a task link and a screen recording - staff asked for these during the 2026 incident

This guide also covers

asana rules not working
asana rule not triggering
asana rules stuck processing
asana automation not working

Still not working?

If Asana keeps failing, you're not alone. See every Asana problem users report or the alternatives people switch to.

Other Asana errors