andygunther | 2016-11-11 22:10:03 UTC | #1
From time to time, we are getting this response back when trying to parse out what can amount to thousands of conversations for a day:
Error calling GetConversationsConversationIdDetails: {"status":500,"code":"internal.server.error","message":"An unexpected error was encountered which prevented it from fulfilling the request.","details":[],"errors":[]}
Is there any reliable or smart way to deal with this?
We look specifically for a 429 response, sleep, and retry in an exponential loop. Would it be advisable to do the same thing for a 500 response?
tim.smith | 2016-11-11 22:23:39 UTC | #2
When you get a 500 back, you didn't do anything wrong (probably), but the server had some kind of problem fulfilling your request. It should be fine to retry the request in hopes that the error condition was transient, but not indefinitely. If you're seeing 500s on a regular basis or in a consistent manner, I would open a ticket with Support for it to see if there's a specific condition or issue that can be fixed.
andygunther | 2016-11-11 22:38:19 UTC | #3
It's fairly consistent 500s and 504s. But, not enough for me to want to spend time with Support :slight_smile:
If I find I can't code around it, I'll open a ticket (note: last time I opened a ticket and mentioned the API, they punted me to the forum right away, stating they don't handle API issues)
andygunther | 2016-11-11 23:37:25 UTC | #4
For what it's worth, since I added rate limit logic to stop before I reach a 429 error condition, it seems to have cleared up the 500 and 504 errors. So, that was either a coincidence, or constantly pounding the API so frequently that we are getting a lot of 429 errors was causing other issues...
system | 2017-08-28 19:28:43 UTC | #5
This post was migrated from the old Developer Forum.
ref: 619