Hey,
We have had a perfectly working integration with the API for a few years now and suddenly yesterday, we started receiving ‘No Authorization’ errors when creating tasks, adding tags or creating subtasks. The issue is that it seems completely random. I execute the same code and sometimes it creates the task but fails when adding the tag(s), sometimes it creates the task, adds the tags and creates 4 sub tasks before failing, other times it creates 9 subtasks before failing. I definitely have a valid token (evidenced by the fact that I can create the task in the first place) and there is nothing in the code/task/sub-task itself causing it because otherwise, it would consistently fail at the same point.
401 error looks like: (example of it failing what adding a tag to a task)
Exact same issue here. A Make automation has run smoothly for 6 months and I’m now getting “[401] Not Authorized” error seemingly randomly amongst multiple scenario…
Wow, that does seem odd - since it seems to be happening on different objects at different times, that’s what makes it tough to diagnose. I don’t have any ideas at the moment but I’ll see if I can rustle up some help.
We have seen the exact same thing happen recently - a total of 18 occurrences, with the first occurrence at 2022-10-18 11:40 am Pacific Time and the last at 2022-10-19 09:32 am Pacific time.
There’s no particular rhyme or reason - these 401 errors seemingly occurred at random, irrespective of the project or the operation being performed (e.g., removing a task, adding a task, updating a task, etc.)
Ok I have an update, the intermittent 401’s should begin subsiding. The infrastructure change rollout that caused this was halted and reverted, and it can take a little time for all the hosts to return to the previous state. Please let us know on this thread if you continue receiving intermittent 401’s beyond the next 6-ish hours.
Hi, I just had the same scenario with 401 {“errors”:[{“message”:“Not Authorized”,“help”:“For more information on API status codes and how to handle them, read the docs on errors: Errors”}]}
Somehow im currently also unable to make API calls. I just updated my Python Asana Client Version and made the necessary changes and now I get the error @paulminors mentioned. I also tried refreshing my PAT but this did not help. I tested this for the “Get Project”, “Get Task” and “Get Template” endpoints.
@Noah_Farr, Can you try it in Postman or equivalent tool, just to take the client out of the equation and isolate your call to only the API layer itself?
Sorry for the slow response. Yes, it was working before. The issue just started the other day. But I haven’t had any Zapier errors the last few days so maybe it’s sorted itself out now.
@paulminors@Noah_Farr@Juan_Carlos_Aguilar I just got word from an Asana contact that their engineering team worked on this issue and thinks it should be resolved now. Could you try it again? (And Paul, you may be seeing the results of this fix.)