7 months ago
I have two environments set up for an app I'm deploying, one for staging new features, and another in case I somehow mess up the staging branch.
The latter is set to sleep, so when my app makes a request to my railway app, it gets a 502 error in return as opposed to perhaps keeping the connection for a little longer.
Is there anyway to either allow more time before a 502 is returned, or somehow configure the return message to be more helpful than "Application failed to respond".
I'm tempted to use associate the 502 error with App Waking, but that obviously doesn't seem like the right way to handle this error.
proj id: a83758cd-7f2e-490a-814b-83a31c1dc56d
0 Replies
7 months ago
we are aware of this issue, it's not the user can do to fix it.
I've added your thread to our internal ticket so that I can update you when it's solved.
7 months ago
@jason