Statuses

A status is the label Hookspot shows on a request, a delivery or an attempt, such as Delivered or Skipped. Find the label you see to learn what it means.

Outcomes

Requests, Deliveries and a delivery’s Attempts tab show one of these outcomes:

Outcome	What it means
Pending	Hookspot has not routed the request yet, or your app has not answered yet.
Delivered	Your app answered with a 2xx status.
Failed	Your app answered with another status, or the CLI could not reach your app.
Skipped	No CLI was listening to the source when Hookspot sent the delivery. The detail reads CLI offline.
Rejected	Hookspot stored the request but sent it nowhere. The detail names the reason.

If the CLI stops before your app answers, Hookspot marks the delivery Failed after five minutes.

To fix a Failed, Skipped or Rejected webhook, find it under Failures and fixes.

Rejection reasons

Reason	What it means
No route	The source has no route, or all of its routes or their paths are paused.
Source disabled	The source is paused.
Source deleted	Someone deleted the source before Hookspot routed the request. It cannot be delivered.

Status filters

The Status filter on Requests and Deliveries uses its own words, which differ from the outcomes.

On Requests:

Status	Matches
Pending	Requests that Hookspot has not routed yet.
Accepted	Routed requests. Their deliveries carry the outcome.
Rejected	Rejected requests.

On Deliveries:

Status	Matches
Pending	Pending deliveries that Hookspot has not sent yet.
Sent	Pending deliveries that wait for your app’s answer.
OK	Delivered deliveries.
Error	Failed deliveries.
CLI offline	Skipped deliveries.

Attempt triggers

The Attempts tab of a delivery shows what started each attempt:

Trigger	When
Initial	Hookspot sent the delivery for the first time.
System retry	Hookspot sent it again on its own, as Retries describes.
Manual retry	You retried the delivery in the app.