a month ago
Hi team,
Project: loyal-adventure (db6f0a2c-4258-4181-aef8-decc5db65b94)
Service: alluring-respect (8120d3d9-b320-4cce-8e90-4599101b5c6d)
I've had 4 commits queued for deployment for ~21 hours without progressing:
- 585f6d5 revert(labels): one label per pack, not one per needle (~5 hours ago)
- 202829a fix(pending-prep): exclude service-only orders from prep queue
- 2aec5b9 fix(fuzzy): bidirectional prefix match
- 7a3ebbe fix(fuzzy): HSN didn't match
Currently the ACTIVE deploy is still d13ed7d from yesterday afternoon. Yesterday I saw the "Limited Access — Deploys have been
paused due to a platform outage" banner. Today the banner reads "Builds are slow to progress. We have pushed a fix and are now
monitoring the incident" — but my builds still aren't progressing.
Business impact: this is a Rx label printer running in a live medical clinic. The currently-deployed buggy code is printing 4×
duplicate labels per medication order, which is (a) wasting physical label stock and (b) creating fulfillment confusion. The fixes
I have queued resolve this, but I can't get them deployed.
I'm on the trial right now, with ~10 days / $3.52 of credit left. Planning to upgrade to Hobby in the next few days but wanted to
flag this issue first.
Could you:
- Confirm whether the slow-build incident is still affecting my account specifically
- Share an ETA on resolution
- If possible, manually trigger a redeploy of the latest commit (585f6d5) on the alluring-respect service
Thanks,
Caroline
2 Replies
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
Status changed to Awaiting User Response Railway • 27 days ago
a month ago
Apologies for this canned message but in an effort to help all our customers get back up and running, we are sending this bulk message. As you may know, we had a major interruption to our services yesterday. We've published a post-mortem if you'd like more information on the incident. It describes what happened and what we are doing to prevent it in the future. We are deeply sorry for the impact that it has had on you.
It is taking some time to bring everything back up, but we are working on it as fast as we can. In general, a redeployment should fix most service issues. Due to the volume of customers redeploying right now, builds and deploys may take longer than normal to process.
You can track recovery status here: https://status.railway.com/incident/KVZ1Z8GY
If you are still having other issues that might be related to the incident you can read more here: https://station.railway.com/community/road-to-recovery-post-gcp-outage-builds-d362e48c
Feel free to respond if your question has not been addressed.
20 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 20 days ago