Service: affiliatelinkaudit-app

Environment: dev

Three consecutive deployments of the same commit (1fbf1b1e97c2de81688f827e55e757a19724e81d) have failed or been removed over roughly 90 minutes:

23:14 UTC — FAILED at BUILD_IMAGE

SNAPSHOT_CODE ran for more than 23 minutes.

BUILD_IMAGE then failed with no captured build logs.

Railway returned: “Failed to build an image. Please check the build logs for more details,” but the build-log pane was empty.

23:26 UTC — FAILED at SNAPSHOT_CODE

Repository snapshot timed out after approximately 61 seconds.

23:32 UTC — REMOVED during snapshot

The same repository and branch deployed successfully at approximately 20:20 UTC, about three hours earlier. No application-code changes occurred between these attempts beyond the commit being deployed, and all attempts are for the same commit hash.

Railway’s status page is currently reporting degraded deployment performance and deployments remaining in initialization longer than expected. These failures appear consistent with that incident, particularly the unusually long snapshot stage, snapshot timeout, and build failure with no build logs.

Is anyone else seeing SNAPSHOT_CODE timeouts or empty BUILD_IMAGE logs during the current incident? I’m mainly trying to confirm whether these queued/failed deployments should be left alone to recover when the incident clears, rather than retriggered.