Hey @Ross_Grambo,
This issue is still occurring - I’m up to 172 sync errors since it started yesterday, and they’re still coming in.
I’ll DM you with some additional info.
2 Likes
Hi @Ross_Grambo @Phil_Seeman ,
Has this issue been resolved or is there a workaround on how to get the data which failed?
We have been seeing this issue lately as well and these Asana webhook events are business critical? What is the process to follow when something like this happens?
We can create projects specific subscription URLs but what would this solve?
Thank you!
Hi @AutomationMaster and welcome to the forum,
Asana’s webhooks architecture underwent a pretty major rewrite earlier this year and the sync_error issue basically went away for me at that point. I would recommend writing to api-support@asana.com to get some specific help on your issue.
I’m a bit puzzled by one thing you said, though:
We can create projects specific subscription URLs but what would this solve?
Webhooks at a project level return wholly different events than those at a higher level; they’re not interchangeable. At a project level, you get task-based events; at higher levels you get events on higher-level objects…
Thank you @Phil_Seeman . I am unsure why we are still receiving sync errors, I will contact the support team.
All the way at the beginning of this thread someone suggested to create unique subscription URLs for each specific resource:
From that answer I understood it would help to create a new URL for each project instead of having each project subscription notify the same URL. However, I did not quite understand what exactly this would solve when you get a sync error.
Thank you!
Ah OK, I see what you meant now by your comment.
Joe was just saying that if you include the project id in your webhook, then when you do get a sync error, you’ll be able to know which project it came from. It doesn’t do anything to avoid the sync error, it just gives you some additional tracking data when it does occur.