15 days ago
Project ID: b4a4c027-0c13-48ad-aa90-f0c8daee52cb
Service stuck: dify-proxy (fd645fa7-daad-4f12-ad8f-27d5582daa7e)
The problem: Three deployments are stuck in QUEUED state since 08:30 UTC. The builds finished successfully, but the scheduler cannot allocate a replica to start the containers.
Deployment IDs:
a0a312e8-ec7d-44e6-b868-9c3f86f519b6
6392beb4-d8db-4c38-adc1-e53479a0e091
12597478-771a-4748-b6c4-0a7e7f2b4588
What happened: The same issue hit capabilityeconomics earlier — we cancelled those deployments manually and they cleared. But dify-proxy's QUEUED deployments cannot be cancelled from the UI. The builds are done; they're just stuck waiting for the scheduler to allocate resources.
1 Replies
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
Your dify-proxy service is running again, the latest deployment is active and healthy on 1 replica. The queued ones cleared on their own: your pushes were landing back-to-back, so each deploy queued behind the previous one until the newest built and took over, and the older attempts were dropped. Nothing's stuck now. Please let us know if you still see any issue here!
Status changed to Awaiting User Response Railway • 15 days ago
Status changed to Solved chandrika • 15 days ago