10 hours ago
The p03-postgres16 service in project r33-r10-p02-pg16-20260927 is stuck with two EnvironmentPatches that are blocking all deployments.
Current Status:
Service ID: fedcd1b0-47a5-420b-959a-4fe624bdd1e9
Environment ID: e78e26f7-e5e7-4f75-a13a-1915c9167f46
Service State: CRASHED (0/1 replicas running)
Last failed deployment: 2026-09-27T11:08:03Z (Deployment ID: 98e91ee4-d0d5-4027-8514-c7e470865839)
6+ sequential deployment failures in the past hour
Stuck Patches:
Patch ID: patch:18026bae-ae6c-45d8-ac6e-1d50ad2e4825 (status: staged)
Patch ID: patch:ae0d9d40-6dd7-4a1a-a778-9beff4475a27 (status: applying) - currently stuck mid-deployment
Both patches are preventing any new deployment from completing (SNAPSHOT_CODE step completes, then no further events or logs are captured).
Request:
Please force-clear or resolve these two stuck EnvironmentPatches
Preserve the current service configuration (postgres:16.15 image, existing environment variables, 4GB memory allocation, etc.)
Allow the service to redeploy successfully after cleanup
The issue could not be resolved via AI diagnosis and requires review by a Railway representative; please clear the stalled patches while preserving the existing settings.
Thank you.
2 Replies
Status changed to Awaiting Railway Response Railway • about 10 hours ago
8 hours ago
Please investigate the unresolved environment workflow for this current project. This is a different project/environment from the earlier p03-postgres16 support request.
Project: r33-p03-r4-full-default-20260927
Project ID: e93f48f9-bc4f-4709-9d02-aec845d9cbdd
Environment: production
Environment ID: 268b474b-3f28-4698-a522-d7a3d2093531
Service: p03-remote-postgres16
Service ID: bedfaa0b-a46f-4408-ab79-83b49b27b6b2
The environment patch 734c658b-d8ae-4460-bbb4-f34ebf9a319d has remained applying since 2026-09-27T12:36:08.737Z. A second patch, f83c523e-d21e-4160-8ef6-7fd002a034f3, is staged for the DB service and includes its TCP proxy on target port 5432. The unintended TCP proxy change for p03-r4-full-default has already been removed.
The DB deployment ee457e2b-3cdd-43e8-b9ce-8879f6d84043 reports SUCCESS, and resource metrics remain available, but the dashboard continues to show an applying workflow and no external TCP endpoint has been issued.
Please reconcile or safely resolve the stuck applying workflow, preserve the DB service and its running deployment/data, image postgres:16.15, existing variables and TLS settings, and default resource limits. Preserve the intended DB TCP proxy change so it can be applied after reconciliation. Please do not delete or recreate the service or rotate its credentials. Please confirm when the environment is ready to apply the pending TCP change.
3 hours ago
Hey can you link to the project in question with the issue? I'm not finding a project under that ID.
Status changed to Awaiting User Response Railway • about 3 hours ago