15 days ago
My deployment repeatedly fails at “Deploy → Create container”.
Service: bot-financas-whatsapp
Deployment ID: 0c6dedfa
Date: August 6, 2026
Repository deployment from GitHub.
The build completes successfully and the container image is pushed (59.6 MB), but Railway fails before the application starts. There are no application runtime logs.
I already tried redeploying twice. Railway’s automatic diagnosis also returns “Diagnosis failed for this deployment”.
The previous deployment remains active and healthy at the /health endpoint. Please investigate the container provisioning/orchestrator failure for this service.
2 Replies
15 days ago
Your service's start command contains raw environment variable assignments (including access tokens) instead of an actual application command, and the container runtime is rejecting the token string as too long to be a file path. Remove everything from the start command field in your service's settings, since those variables are already defined in your service's Variables tab and will be injected automatically. Once the start command is cleared, Railpack will detect and run your application normally. Additionally, because the token was embedded in the start command, it may have been exposed in deploy logs, so you should rotate your WhatsApp access token in the Meta developer console and update the new value in your Railway service variables.
Status changed to Awaiting User Response Railway • 15 days ago
Status changed to Awaiting Railway Response Railway • 15 days ago
15 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 15 days ago
14 days ago
As the bot says, you're putting a token instead of an actual command, that's why your deployment isn't running
(You might trying to put a variable but pasted it in the wrong place)
Change your start command with the actual command to run your application