Hey there! We've found the following might help you get unblocked faster:

• 🧵 Updating shared variable doesn't redeploy
• 🧵 502 error after container build
• 🧵 Error while running the Node JS project after deployment

If you find the answer from one of these, please let us know by solving the thread!

Hmmm, this appears to be loading on my end just fine.

Is it still happening for you?

It resolves when I restart the server - so I did that an hour or so ago and it resolves immediately.

Interesting hmm.

Next time this happens can you share the link to the service not responding?

It happened twice more today, must be something in my app, but have no logs reporting any issues, just sudden 502 errors. Here's a screenshot of the screen I seen my health check. I need to restart it right away so the worker resumes so can't exactly share a link of it being down.

From the 6h CPU metrics, it looks like your app is heavily CPU constrained. Given that Node apps can typically only use 1 vCPU due to their single-threaded nature, I would suggest adding more replicas.

ok perfect thank you, increased to 4 - will monitor this and add more if needed. Thank you!!

No problem!