As title states!
Rules, manual and auto-triggered, that were all running this morning across our entire asana environment, now all fail to run and stay stuck in ‘processing’ and can be seen eternally processing in the task view. Odd that it happened today out of nowhere. Any help? Thoughts?
Welcome, @Jonny_Ochoa, and sorry.
I haven’t heard any similar reports, so I think your best bet is: Try these troubleshooting steps, then please create a support ticket: see How to contact Asana Support.
Thanks,
Larry
Bumping this as the issue is still unresolved.
We’ve gone through all of the recommended troubleshooting steps, and Asana Engineering has confirmed they’re aware of the issue and working on a solution. Unfortunately, this is now having a significant operational impact on our business because of how heavily we rely on Asana automation rules.
Multiple teams depend on these automations for day-to-day workflows, and we can’t effectively operate without something similar in place. I wanted to make the broader community aware in case others are experiencing the same issue.
If this isn’t resolved soon, we’ll have to start evaluating alternative products or solutions. This also isn’t the first time we’ve experienced an Asana backend change unexpectedly breaking existing automation rules, which makes it increasingly difficult to rely on these workflows for business-critical processes.
From what we can tell, the issue appears to have started around the rollout of the new AI agent functionality. Regardless of the cause, we really need Asana to prioritize stability of existing functionality when introducing new features. Breaking established automation workflows without warning has a very real impact on businesses that have built their operations around the platform.
Same for our team! The rules are stuck on “Running” and won’t push through. Any help, please?
The same thing is happening for us. I created a support ticket last night about this.
Our rules first broke on the 12th, but only on one particular project. Rules were firing inconsistently and I was troubleshooting what might have gone wrong. Nobody had changed anything about the rule prior to it breaking. The rules would sometimes say “running” but then that would disappear and none of the rule actions had posted. Other times, the rule would say it had posted, but it would behave unexpectedly. (For instance, rules that created new tasks would create a private task instead of the ordinary public one, but nobody in the company was getting the notification to grant access.) My suspicion was that this update broke something about the rules, as were seeing errors in the rule history that said the rule had failed because “Could not take action because the rule owner doesn’t have access.” However, nothing about the rule owner’s access had changed prior to the rule failing, and switching the rule owner to an admin user who was also a “project admin” made no difference.
Then, starting yesterday, rules just wouldn’t run at all, not even the manually-triggered ones. Today, same thing. Rules are just sitting there saying they are “running” and nothing posts. What was already disruptive before has become entirely more disruptive now.
Hi everyone,
Thanks for raising this. I wanted to let you know that I’ve already reported the issue internally. Our internal team is actively investigating this behavior, and I’ll circle back here as soon as I hear back from them with any updates or next steps. In the meantime, I truly appreciate your patience. 
Thanks for your detailed response! Exact Same problems here. We were all, in many different teams, using automations and triggers all morning until an hour came where all those same rules and automations started infinitely running. Sorry it’s happening to more people, but also glad to know we aren’t alone in needing a solution!
Hey everyone, our team is on it! To make the investigation smoother, we’ll need the rule IDs (must‑have) and any videos you can share. These details will go a long way in helping us find the root cause. Thanks so much for your support! 
Good to know, I’m happy to provide that. Would it be best to send those here or update the support ticket with that information?
A bunch of our rules that were triggered several hours ago just ran in the last 5 minutes. Not sure what you guys just did, but something worked just now!
Another issue I’ve encountered several times is that rules stop working or become inactive in some client environments.
In a few cases, we noticed this around a Trial → Paid or Paid → Trial transition, so I initially wondered whether the plan transition could be a factor. However, we have also had transitions where this did not happen, so I don’t want to assume that the transition is the root cause.
This causes significant trouble for clients because their automated workflows stop running, and they may not realize it immediately. In some cases, we have had to manually identify and reactivate the affected rules, which can be quite time-consuming and disruptive
Please help me understand what can be the possible reason. And how can we activate the rules without manual interventions.