3 months ago
The new deployment hasn't started yet after pushing the updates to the GitHub repository. It’s been over two hours and I’m still waiting for it to begin.
4 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
3 months ago
Was this pushed to the repo by a user that is not in your Railway workspace?
Status changed to Awaiting User Response Railway • 4 months ago
3 months ago
No, it was me, I updated my private repository.
Status changed to Awaiting Railway Response Railway • 4 months ago
noahd
Was this pushed to the repo by a user that is not in your Railway workspace?
3 months ago
No, it was me, I updated my private repository.
Status changed to Awaiting Railway Response Railway • 4 months ago
3 months ago
Thanks, that rules out the cross-workspace-author case. Autodeploy on this service has recovered: your pushes to experiment-bd+admin_panel have been building and deploying normally since, and your latest commit (af359dcb) deployed successfully at 20:56 UTC. The earlier 2-hour gap was a transient delay in picking up the GitHub webhook, not a config problem on your repo.
If a future push ever fails to trigger within a few minutes, you can hit Deploy on the service to force it while the webhook catches up. Let us know if you see another stall.
— Angelo
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved Railway • 3 months ago