Skip to main content

Retry a failed release

A release can fail before it merges: its checks went red, the merge hit a conflict, your repository host refused it, or no node picked it up in time. Retry sends that same release again. It keeps its pull request, runs the failed checks again, then merges as before. Nothing new is added to it, and no second pull request is opened.

Use Retry when the cause is fixed outside the code, such as a flaky check or a node that was offline. When the fix is new code, merge it and select Release instead: a new release ships everything that waits, and closes the pull request of the failed one it replaces.

Who can do this: anyone who may release to that stage. That is edit access to the project, unless its pipeline names who may release.

  1. Select Tasks in the sidebar, then the project in the Projects tree.

  2. Select the Pipeline tab. The stage strip sits under the top line. A Release step whose last release failed shows a red icon. Hover it to read where it failed, such as Failed at gate › CI.

  3. Select the red Release step. The row above the list names the step, such as Dev → Production, and Checks before Production below it lists the checks the release ran. Read which one failed.

  4. Select Retry in the row. It shows only for a release that failed before its merge and that no newer release has replaced. Hover it: Re-run the failed checks on the same PR, then merge it.

    The release row of the Pipeline view: Dev → Production, 17/17 shipping, cost, tokens and age, then Now, Release 17 and Connect deploys. No release has failed here, so Retry is not shown

  5. Watch the row. The release goes back to Queued, then Releasing, with a running line under the row. Once it merges and deploys, Production shows the new version.

  6. If it fails again, read the checks under the row and select Run, where shown, to open the run and its log.

If the row says This one can't be retried. Release again., the release failed after its merge or for a reason a retry can't fix. A newer release replaced this one. means someone already released again. In both cases, select Release.

You don't always need Retry: if someone merges the failed release's pull request by hand, the next deploy that carries it marks the release live by itself.

The capture above shows the row with nothing failed: the organization it was taken in had no failed release, so the Retry button could not be photographed.