Skip to content
How can I retry an exact pinned commit after a Docker Hub 429?
bortal99
OP

a month ago

My staging frontend deployment failed when Railpack received HTTP 429 TooManyRequests while fetching Docker Hub’s alpine:latest manifest. The previous deployment is still serving. The failed deployment reports canRedeploy=false, and its menu only offers Remove. The service is connected to GitHub and pinned to a specific commit that has passed CI. What’s the supported way to retry building that exact commit without changing the pin or deploying a different revision? Does “Deploy latest commit” honor the configured commit pin? I found serviceInstanceDeployV2 with commitSha in the API docs, but that operation isn’t exposed by the Railway MCP tools available to me. Is there a dashboard or MCP option for this? Thanks!

Solved

1 Reply

Status changed to Awaiting Railway Response Railway • about 1 month ago


chandrika
EMPLOYEE

a month ago

Apologies for the trouble. The 429 came from an incident affecting image pulls from Docker Hub, which has since been resolved: incident timeline.

That failed deployment can't be redeployed because it never finished building, so there is no build to reuse, which is why its menu only offers Remove.

"Deploy latest commit" does not honor a commit pin. It deploys the head of the connected branch, so it would not build your pinned revision. The dashboard has no general option to deploy a specific commit SHA, and the Railway MCP tools don't include a deploy-by-commit tool either.

The supported way to build that exact commit is the public API's serviceInstanceDeployV2 mutation with commitSha set to the pinned SHA, along with the service and environment IDs. It builds that revision and leaves the pin unchanged.


Status changed to Awaiting User Response chandrika • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...