Retry a failed delivery

Find a GitHub webhook or Zof event that failed, and send it through again. It takes about 3 minutes, and you need to be a company admin in Zof and an admin of your GitHub organization.

A delivery is a webhook GitHub sends to Zof, or an event Zof sends to its other services. Zof retries a failed delivery on its own, waiting a little longer after each of the first attempts. One that still fails, or that can never succeed, becomes Failed and waits for you.

Before you start

• Your GitHub account is linked in Integrations, and you're an admin of the GitHub organization. If it isn't linked, the page asks you to link it; if you're linked but not an org admin, it says "Only a GitHub org admin of" the organization "can see deliveries."
• To retry, you're also a company admin in Zof. Otherwise Zof refuses the retry with "Couldn't retry: You need to be a company admin to do this. Ask a company admin."
• The Zof GitHub App is active on GitHub. While it's suspended or waiting on GitHub, the tab says "Retry is off while the Zof GitHub App is suspended or waiting on GitHub."

Find the delivery

If the GitHub card shows App removed or Needs review, follow Recover an unavailable connection first. Retrying a delivery cannot repair that connection.

1. In the sidebar, open Integrations.
2. Open the GitHub card, then the Events tab.
3. With more than 10 rows you can filter Needs attention by status or time.

Each row shows the status, what happened, where, when and why. What happened is named in words, such as Pull request opened; a job Zof has no name for reads Zof background job. Delivered lists what went through, Zof's own jobs included.

The count and the page's status word cover the last 7 days and rows you can act on. A refusal because a newer commit replaced it, or a failure Zof won't replay, stays listed under Earlier, or nothing to fix.

For support, open a row's Details and choose Copy reference. Details also says how many times Zof tried, or "Attempts not reported" when the Zof GitHub App didn't say. It never shows 0.

Retry a failed delivery

1. On the delivery's row, click Retry.
2. The tab says "Retry queued. It goes through every check again."

If the same work was already waiting, it says "Retry queued: the same work was already waiting, so it runs now." The row shows Retrying until the delivery goes through.

Retry a refused delivery

A delivery refused for Installation not active or Repository not installed can go through once the cause is fixed.

1. Fix the cause on GitHub. Resume or reinstall the Zof GitHub App, or add the repository with Choose repositories on GitHub.
2. On the delivery's row, click Retry.

Zof checks the delivery again from the start.

Check that it worked

1. The delivery leaves the list once it goes through. When nothing is left, the tab says "No deliveries need attention."
2. If the delivery was about a pull request, its Zof / Control check on GitHub updates.

When there's no Retry

The row says why there's no Retry:

A row with no Retry may offer Open change instead.

Company admins also get a "Webhook deliveries failing" notification in the console's bell when a delivery fails for good. It says to retry it from Integrations.