Rollback/redeploy button fails silently for non-bridge jobs

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The rollback/redploy buttons are failing silently for non-bridge jobs under the following conditions:

• If the environment is protected and the user does not have permission to deploy, the rollback/redploy button is visible and can be clicked, but it fails silently (see image below). The related API call shows a 404.
• If the job associated with the deployment is not the latest instance of the job in the pipeline, then the attempt fails with a 422 shown in the browser's devtools, but with no error displayed in the GUI.

Related:

• #556036 (closed) (similar silent failures for bridge jobs)
• #541573