Getting a lot of 500 Errors when checking the Events endpoint

Our solution requires downloading tasks for integration with our Filemaker solution and keeping those tasks in sync. We do this by checking Asana’s Events endpoint and getting events per project, per user. We have 3 users and approx 40 projects. We record the sync tokens per project per user and poll the Events endpoint every 10 mins to get changes.

This solution had been working fine for approximately a year but since about 3 weeks ago we’re getting a lot of 500 errors. It’s hard to diagnose what’s causing the issue because we get 500 errors only on some projects while others get events successfully. Yesterday the errors were consistently showing up for one project today the 500 error is showing up on 10 projects. There were a few days this week when there were no errors at all.

I’ve submitted a ticket with Asana support but no response yet. Any ideas on how to diagnose this issue or what to change?

Here’s an example of the error message from Asana.

{
“errors” : [ {
“message” : “Oops! An unexpected error occurred while processing this request. The input may have contained something the server did not know how to handle. Usually waiting and then retrying the request once fixes this. If the issue is persistent, please contact api-support@asana.com and include the error phrase from this response.”,
“help” : “For more information on API status codes and how to handle them, read the docs on errors: Errors”,
“phrase” : “30 faulty badgers kneel terribly ably”
} ]
}

@BRA_Assistant - welcome to the forum! Not sure when exactly your issues began, but there was a major outage on August 1 that affected many things, including events. Not sure if that is a root cause of your ongoing issues, but the timing is suspicious and does seem to line up. Hopefully support gets back to you soon; make sure you don’t respond to your own ticket as that will bump it to the bottom of their queue.

Thanks for the tip about not responding to my own ticket!

The errors unfortunately started before Aug 1 outage, we had a string of them from July 24th.