SP
Services weren't reachable when the deployment failed
(id: 4b49be5c-8a2a-44f2-90e8-28a9de6c457f)
Yesterday, we noticed that some of our services weren't reachable when the deployment failed. Isn't railway make sure that the old container will be killed only after the new one is live?
Also, the service was returning gateway timeout for few minutes once the deployment succeeded.
We are using railway on production and this really affects our users. Please look into this issue.
30 replies