502 errors on HTTP endpoints - why?
The other day I was notified of a 502 error code thrown by an HTTP endpoint. This happened twice within a 30-minute timeframe. This endpoint is called hundreds of times a day by various parts of our internal business logic, and since I set this up some time last year, this is the first time I've seen this 502 error. For it to happen twice in 30 minutes makes me just a hair nervous.
I couldn't find any reference to 502 error codes in the Convex docs. Just curious if there's a simple explanation that will help me address this in the future.
5 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
i'm facing the similar issues since this week. random 502s as well. good to know i'm not the only one.
For now I've implemented an auto-retry with exponential backoff, and haven't seen any more 502s since then, but I'm still curious where they might be coming from and what (if anything) I can/should do to prevent them.
Answer received via email:
Our traffic management system has experienced some periodic issues as we've scaled up to accommodate a large number of new customers over the last few weeks. We're working on increasing resources and optimizing our systems to handle the increased traffic without future incidents. The 502 is not related to function concurrency being exceeded; we provide a more descriptive error message in that case.(I had somehow thought that it might be an undocumented response re: exceeding concurrency limits, which explains the second part above)
Suffering from success
i think with the introduction of chef their stystems are being hit even more. agreed: suffering from scuccess part. i feel now is the time for real convex testing. and i also anticipate this will happen more often. time to hire more devops staff 🙂