Payload CMS build stuck at BUILD_IMAGE with no output
knightlightdigital
PROOP

a month ago

My Payload CMS service (rpuls/payload-3-boilerplate, master branch) is stuck in a persistent build failure loop. The build fails at the BUILD_IMAGE stage with no error output.

Details:

  • Service: payload-CMS (ac601516-601a-4cbb-b177-17cc56dc37c9)
  • Project: Cosmos & K-Dramas (65fa7092-9d72-40bb-965b-6dcb8f190efa)
  • Environment: production
  • First failed deployment: 5376526d-04d4-47d7-9303-3e8a978171a9 (2026-07-19 17:26)
  • Latest failed deployment: 66c42cc9-b300-4b56-a113-1fe278ea3f95

The build logs show only "scheduling build on Metal builder" with no provider detection, install step, or build output. The same commit (8b425f8) built successfully at 16:39 UTC on 2026-07-19, about 1 hour before the failures started. I've redeployed 8+ times over the last hour with no success.

This appears to be a transient infrastructure issue since:

  • The commit is valid (only minor dependency bumps)
  • The same code deployed successfully very recently
  • Multiple consecutive deployments all fail identically at BUILD_IMAGE with no output

Please investigate the build infrastructure for this service.

Solved$20 Bounty

0 Replies

Railway
BOT

a month ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 1 month ago


Status changed to Solved knightlightdigital about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...