21 days ago
I have a persistent "Deployment failed to build" warning banner displayed on my backend service card. However, this warning doesn't reflect the actual state of my deployments.
What I'm seeing:
The warning banner appears on the service card in the dashboard
All recent deployments complete successfully (build passes, image pushes, healthcheck succeeds)
The service is active and working correctly
The latest deployment shows as successful when I click into it
Build logs from latest deployment show success:
You reached the start of the range
Feb 12, 2026, 8:52 AM
scheduling build on Metal builder "builder-dwbaud"
fetched snapshot sha256:c151e9b396049011409b25e9844d2a25463580f8b051303632ad4349e51d52d7 (186 MB bytes)
fetching snapshot177.3 MB4.9s
unpacking archive190 MB1.5s
internal
load build definition from backend/Dockerfile
0ms
internal
load metadata for docker.io/library/node:20
150ms
internal
load .dockerignore
0ms
1
FROM docker.io/library/node:20@sha256:94a5714e6b243bf37a1767e637996302fadd9443327f5bdbf0179758fe70cacd
12ms
internal
load build context
0ms
7
RUN npm run build cached
0ms
6
COPY . . cached
0ms
5
RUN npm ci --prefer-offline --no-audit cached
0ms
4
COPY package*.json ./ cached
0ms
3
RUN apt-get update && apt-get install -y python3 make g++ && rm -rf /var/lib/apt/lists/* cached
0ms
2
WORKDIR /app cached
0ms
exporting to docker image format
2s
containerimage.descriptor: eyJtZWRpYVR5cGUiOiJhcHBsaWNhdGlvbi92bmQub2NpLmltYWdlLm1hbmlmZXN0LnYxK2pzb24iLCJkaWdlc3QiOiJzaGEyNTY6Mjk0MGZlZDY3OTcxYWZkODMxYTI1Mzc5MjY1ZTdhYzVlNjkwN2ZhMjg5MDI3YWFmNmE0Yjg2MjE0OGQ3YmRkYiIsInNpemUiOjI5NjUsImFubm90YXRpb25zIjp7Im9yZy5vcGVuY29udGFpbmVycy5pbWFnZS5jcmVhdGVkIjoiMjAyNi0wMi0xMlQxNDo1NzoyM1oifSwicGxhdGZvcm0iOnsiYXJjaGl0ZWN0dXJlIjoiYW1kNjQiLCJvcyI6ImxpbnV4In19
containerimage.config.digest: sha256:e56d6a8d9736689790d84458ccef6ab6f96bd581fff1e60a286381bc0613dad5
containerimage.digest: sha256:2940fed67971afd831a25379265e7ac5e6907fa289027aaf6a4b862148d7bddb
image push459.9 MB1.4s
==================== Starting Healthcheck ====================
Path: /api/health
Retry window: 5m0s
[1/1] Healthcheck succeeded!
What I've tried:
Multiple new deployments via git push - warning persists
Verified the deployment status shows successful
Confirmed the service is active and responding
Expected behavior:
The warning banner should clear after a successful deployment.
Actual behavior:
The warning banner remains stuck on the service card even though deployments succeed. This has persisted for several weeks.
Is there a way to clear this stale warning, or is this a known UI bug?
7 Replies
Status changed to Awaiting User Response Railway • 17 days ago
16 days ago
I don't have any unread notifications. I was actually referring to the warning sign on the service card (see screenshot attached). Appreciate any help you can offer. Thanks.
Attachments
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
I know we had a bug in the past about a failed deployment warning sometimes not clearing. Did you in fact have a failed deployment before the warning sign first appeared?
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Yes, I did. After fixing it and redeploying successfully, the warning still didn’t clear. I experienced something similar in another Railway account for a different project, but that one resolved on its own after a few weeks. This case is different — it has been months, and the warning has still not cleared.
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
Thank you for the report. We have created a ticket to track this UI discrepancy.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
Thank you.
Status changed to Awaiting Railway Response Railway • 16 days ago
9 days ago
Hi, just following up on this as it's been 7 days and I haven't received an email confirming a ticket has been opened. Thanks.