Hi,
I am trying to run a Make/Integromat automation. This previously used to work but now I am getting a [403] error from Asana, we have two method to check.
First, we trying to change the project. if the task project is same the project we need to change section it’s not work(P1), Although if the task project is another project we need to change it’s work(P2).
Same error here! What’s wrong??
And if you do the same thing manually in Asana, you don’t run into any error?
Yes, There is only MAKE automation run with error 403 since 21 Dec.
1 Like
Any workaround or time to fix @Bastien_Siebman ?
@Ming_Phupha_Sungden @OlexiyZalevskyi @Mario_Beteta I don’t think this is related to your use of integrations; I think it’s actually a new bug in the Asana API itself. See this forum post for a similar report. I’m following up with my Asana contacts.
Hi, Looking into this but for the time being I want to point out that projects recently got a setting to restrict who can add tasks to a project and this can impact the “source” or “target” project. This error was introduced to indicate that.
We mentioned this in this post, but I’m realizing now that it was not included in the title and could be missed. Will work on clarifying that.
Still, I would not expect this to impact your integrations until someone explicitly changed this setting, but I could be missing a behavior change. Can you verify that you are an Editor in both the source and target projects? (note, the API / integration permissions will be that of the person who originally set up the integration unless)
Two questions for you:
- Do you mind sharing your user ID or domain user ID so I can help debug? You can find this by going to your “profile” page and it should be the ID appended to the url “https://app.asana.com/0/profile/{YOUR ID}”
- Can you clarify this part a little more?
“if the task project is same the project we need to change section it’s not work(P1), Although if the task project is another project we need to change it’s work(P2).”
Based on your later screenshots, the input seems to be the same but with different results. Would like to understand better what changed in between!
Thanks!
Hi,
The error message you posted in the title is expected in the case when a task is being added to a project and either the source or target project have a restriction on who can share tasks with other projects. This is a relatively new project permission. Screenshot from the web app below and some more detail in this post: [ Upcoming ] Custom field permissions value editing: Add new restrictions on custom fields
We think there was a change introduced which caused this permission to be incorrectly applied to section changes and tasks with due dates, so we have rolled it back and will be sure to fix the problem before releasing again.
Thank you for reporting the problem here. My apologies for the inconvenience this caused. Please let us know if this resolves the issue for you.
2 Likes
@John_Baldo Good news - heard back from one of my affected customers that it’s working for them again.
2 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.