Briefly describe (1-2 sentences) the Bug you’re experiencing:
When duplicating projects that use external rules (Flowsana in my case) via browser or API, rules with external rule actions no longer work or store their value and, show “This action is no longer valid. Please remove it and try again.”
Steps to reproduce:
- Create a project
- Add a rule with a Flowsana action
- Duplicate project from project context menu or via API.
- See that the Customize button is red with error icon, and expand pane to see that rule is broken.
Both browser and API
What version of Asana are you using (Basic/Premium/Business/Enterprise)?
Upload screenshots below:
This worked flawlessly up until the last couple weeks, but just noticed it a couple days ago. I unfortunately don’t use any other external rules to see if they also break. However, I have reached out to Flowsana support, and they’re not aware of anything on their end that could be causing this, so I suspect this is a bug or backend change on Asana’s end.
EDIT: I’ve also tried rebuilding the rules in question within my “template” project, and sadly this doesn’t solve the issue.
@sasha_f @John_Vu Maybe you could check into this?
I guess nobody from Asana has looked into this?
I’ve hopefully just manually updated all my rules for the last time.
Instead of waiting for a response from Asana, I’ve created a much simpler custom solution in Airtable. We will be significantly scaling back our Asana usage next month if all goes well with our pilot test.
EDIT: Turns out, you can just update the rule instead of removing/readding it, which is a bit of a timesaver, in case anyone else runs into a similar issue.
Hi @Frank, sorry for missing this! I’ve reported this to our Developers so they can take a look, and as soon as I have any updates I’ll get back to you
@Vanessa_N I get a similar message when using the external action from iDO Things, specifically the “Unmark as milestone/approval” action. It was working fine a couple of minutes ago but now gives me this error.
Hi @Joseph_Juarez, welcome to our Community, and thank you for the additional information. I’ll add this to our Bug report!
Hi everyone! Our Developers are investigating this report, and they believe these are two different issues:
Flowsana: the team responsible will get in touch with folks at Flowsana to correct the problem
iDO: it’s likely that this was related to the AWS outage we had. If you re-create the rule, it should work now! Let me know if this is not the case