Anyone else having major issues with the new update to make rules run using the owner’s permissions?
I am a super admin for my account and essentially our Asana project manager. I create all of the rules we use spanning several projects. The recent update has caused so many issues. Not only are several of my rules not running properly, but I’m not notified at all when they fail or partially run. There are zero details on why they failed/partially ran. And I’m being added as a collaborator on every new task that is created because I’m the owner of the automations.
I never got an email from Asana saying which rules will be affected and how to fix them before the rollout (per this article: Asana Help Center ).
There also appears to be no real way to fix the issue. I’m an owner/Project Admin on all the projects with the rules I create. I’ve created all the custom fields that are part of these rules. There is nowhere I can see where I am lacking permissions in any way that would cause these rules to fail.
This update has halted productivity in certain areas and will only get worse the longer the issue persists.
Any one have suggestions on what I can do here? Am I missing something?
I’ve already opened a case with the Asana IT team. I’m waiting to hear back, but I’m not hopeful.
Hi @Allison_Logan
You can check in your rule history about why rule is failing
Steps:
- Open rule
- Navigate to 3 dots on top right
- Click on Rule history
This doesn’t help. It just says the user didn’t have permissions. But the user is the onwner and project admin. And the super admin of our asana. So what permissions do they need?
Hi @Jessie_Wood and @Allison_Logan ! Thank you for raising this. I know the update has been challenging. Even as a Super Admin, it’s important to be explicitly added as a member of each project where the rules run, since rules can fail if the owner isn’t listed as a project member. It’s also worth double‑checking that all custom fields used in your rules are shared across projects, because locked fields tied to another team can cause failures. In some cases, deleting and re‑creating the rules under the new permissions model can clear hidden mismatches. And if the rules are meant to run under a team’s context, having a project owner re‑create them ensures they execute with the right permissions. Appreciate you both bringing this up. It’s helpful to surface these issues so we can troubleshoot together.
Ren
This has also been causing havoc for us, and I have not been able to solve it.
Our rules started failing on August 13. In the rule history, it says that no action was taken because “the rule owner doesn’t have access.”
Nothing had changed about the rule owner or their access to the projects that were involved.
It did not help to update the rule owner to an admin user who was also a project admin on that project and all related ones. Rules were still failing.
Rules to create a new task would sometimes fail to run, and sometimes they would run but create a “private task” that nobody in the company could see. Multiple people requested access to the private task, and nobody got the notification to grant access.
Creating a new rule as a workaround didn’t help, as the new rule was also creating “private tasks.” The only way we found to get around this was to add collaborators to the tasks so that people could see the task and get access to it, but this now bombards the team members’ inboxes with countless notifications that they didn’t used to have to see.
I have raised a support ticket and I sincerely hope this can be resolved.
If you receive any response from team that solves the issue do let us know as well
Our Asana rules started running again normally across all projects and all users on Friday evening. Things have worked normally since then. However, Asana Support doesn’t seem to know what they did to fix it, because I got a reply to my ticket on Sunday that said,
I was able to replicate the setup on my end, but I’m not seeing the same behavior you described. To help determine whether this is isolated to your account or affecting other users, could you confirm whether you’re the only person in your organization experiencing this issue, or if other users are seeing the same behavior with rules?
In the meantime, the behavior you’re describing may be related to a browser or local environment issue.
It’s not surprising to me that they were unable to replicate the issue, since they were responding on Sunday to an issue that had been fixed on Friday, but it IS surprising to me that they didn’t know what they had done to fix it.
My theory is that it must have been a different team who solved it? When the community moderator posted here that Asana was looking into it, I assume someone at Asana later fixed whatever was broken. Not sure why that would not have been communicated to the agent who handled my support ticket. 
Hope you get your issue figured out! I saw your other post on the “All Rules Stuck in Processing” thread. I wonder if it might be worth starting a support ticket of your own for that, since it seems slightly different?
