I would suggest you remove and then re-add the repo from the service, and then do a Cntrl + K -> Deploy latest commit to see if it fixes the issue of the option not appearing on the context menu.

Well this is not something the community can help me with, the link to redeploy is missing from the dashbord, so that is a job for the Railway team.

It is there on all other then the latest failed job, and it has been there before, so i just think it is a small bug in the dashboard.

This looks like a UI bug - the redeploy option disappearing specifically on the latest failed deployment. Railway team will need to fix it on their end.

For now, use** CMD/CTRL+K **→ search "Deploy latest commit" as a workaround until it's patched.

Still no response from the team here, thats pretty bad.

Hi there let me see if i can help. This is a product/UI regression, not a confirmed security issue. The failed deployment context menu only exposes View logs and Remove, but does not expose a Redeploy or Deploy latest commit action. The user is an authorized project user trying to redeploy the latest failed commit. Since Railway staff suggested using CMD/CTRL+K and searching for Deploy latest commit, the redeploy capability still exists elsewhere, but it is missing from the expected deployment history context menu. Impact: authorized users cannot easily redeploy a failed commit from the deployment history UI and must use a workaround through the command palette. Security impact: none confirmed. No evidence of unauthorized access, privilege escalation, or sensitive information disclosure.