2 months ago
Subject: Build stuck on Metal builder "builder-puabzb" - heartbeat timeout
Project ID:4822bf23-a9f0-4146-87aa-adabf7e43f61
Environment: production
Service: everydayApi2025
Problem:
- Builds зависають з вчора (2026-03-24)
- Зависають на етапі
unpacking archive→BUILD_IMAGE - Помилка: "activity Heartbeat timeout"
- Той же builder
builder-puabzbпостійно використовується - Код не змінювався, раніше працювало без проблем
Failed deployments:
cc5922cb-0df3-46fe-919d-06c4c32835c9(2026-03-24 22:39)d898221e-7ee5-49d3-9ca4-95e92d673447(2026-03-25 07:36)0c0069d5-293f-46df-8964-dfe048ce8a41(2026-03-25 15:41)
Repo: dmitrykulinichev/everydayApi2025 (dev branch)
1 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open Railway • about 2 months ago
2 months ago
Hi @dmitrykulinichev 👋
Thanks for the detailed report — this is very helpful.
It looks like your deployments are consistently getting stuck on the Metal builder (builder-puabzb) during the unpacking archive → BUILD_IMAGE stage, eventually failing with an activity heartbeat timeout. Since you mentioned there were no code changes and it previously worked fine, this strongly suggests an issue on the builder side rather than your project configuration.
What’s likely happening
- The specific builder (
builder-puabzb) may be in a degraded or stuck state - The repeated assignment to the same builder increases the likelihood of consistent failures
- The heartbeat timeout indicates the build process is no longer responding internally
Recommended steps (quick fixes)
- Trigger a fresh deploy (this may assign a different builder)
- If possible, try:
- Making a small dummy commit to force a rebuild
- Redeploying from a different branch or via CLI
- If the issue persists:
- Try clearing build cache (if available)
- Duplicate the service to force a new builder allocation
Internal note
This likely needs builder recycling or reassignment on our side. We’re flagging this builder (builder-puabzb) for investigation.