API Errors 500 and 520

Hi, guys!

I recently refactored my API function to get data from Monday to the new API version. However, I am seeing an increase in failure rates. Sometimes, the error is 500, and other times, it is 520. These days, I am using the 2024-01 API version.

Is there something that we can do to understand why this is happening?

Is this a 500 or 520 within the errors object of a GraphQL response (which returns with a 200 HTTP status code)?

Or is this an actual HTTP 500 / 520 response?

Does it apply to any random query or specific queries?

Also technically 2024-01 is not officially stable - its entirely possible that until January 15th they have not ramped up its capacity. I’d still only be using it for validation at this time, with 2023-10 being set as production.

1 Like

No. It is the HTTP status code. I am receiving the following message:

Error: Data Source Error: DataSource.Error: Web.Contents failed to get contents from ‘https://api.monday.com/v2’ (520): DataSourceKind = Web DataSourcePath = https://api.monday.com/v2 Url = https://api.monday.com/v2. RootActivityId = 885beec7-fd95-4e6f-852e-29f8f2d53acd.Param1 = DataSource.Error: Web.Contents failed to get contents from ‘https://api.monday.com/v2’ (520): DataSourceKind = Web DataSourcePath = https://api.monday.com/v2 Url = https://api.monday.com/v2 Request ID: 595a8b71-66d3-4acb-b991-c9c938a5feef.

Random queries. Sometimes they worked, sometimes they did not.

I will try to use the 2023-10 version to avoid these problems.

Definitely report this to appsupport@monday.com even if you’re not creating an app. Best way to get things to the API team.

This doesn’t look to be an issue with your queries or what you’re doing, and is an error upstream of the API servers themselves. Based on my experience. But again, don’t work for monday.com but know enough to be able to make bad hypotheses.

2 Likes

Thanks a lot for your messages!

1 Like