Skip to content
WebsitePlatform

Statuses

Understand request outcomes, rejection reasons and retry triggers.

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.

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

Outcome What it means
Pending On a request, Hookspot has not routed it yet, or a delivery is unfinished. A delivery reads Pending · Queued or Pending · Sent instead.
Delivered Your app answered with a 2xx status, or a CLI without --forward-to answered 200 itself.
Failed Your app answered with another status, the CLI could not reach your app, or a retry found no listener to go to, as Retries explains.
Skipped No listener received it. The detail reads No listener.
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 at least 5 minutes after sending it. If the CLI keeps listening and no answer arrives, Hookspot marks it Failed at least 30 minutes after sending it. An answer that arrives later still counts.

A delivery becomes Skipped for one of these reasons, and only a retry sends it. The detail reads No listener for each:

  • No listener covered the source when Hookspot routed the request.
  • Its listener left, and none took over its waiting deliveries for at least 5 minutes.
  • You paused or deleted its route, source or path before Hookspot sent it.

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

A delivery your app has not answered yet reads one of these.

Status What it means
Pending · Queued Hookspot has not sent it yet, or you just retried that one delivery. A delivery waiting for its first send goes out on its own while its listener stays or reconnects, and its route delivers. Otherwise it becomes Skipped.
Pending · Sent The CLI has it, and your app has not answered yet.

A request reads Pending before Hookspot routes it. Until then it has no new deliveries, so it adds nothing to your monthly deliveries.

After routing, a row on Requests also shows Pending while a delivery reads Pending · Queued or Pending · Sent and none is Failed or Skipped.

A destination’s backlog is its deliveries waiting for their first send. A delivery you just retried reads Pending · Queued too, but it is not backlog.

You see Backlog
Pending on a request Not by itself. Check its deliveries.
Pending · Queued Yes, while it waits for its first send.
Pending · Sent No, as the CLI has it.
Skipped No, as only a retry sends it.

See a destination’s backlog shows where it appears. Queued deliveries and the backlog email says what to do about it.

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.
Verification failed The request’s signature or credentials did not pass the source’s verification.

Requests shows each request’s result in its Verification column. Hover over the result, or tap it, to see the provider or method, the reason and when Hookspot checked.

Result What it means
Verified The signature or credentials matched the source’s secret.
Not checked The source’s verification was off, or the request came from Send test request.
Failed verification The signature or credentials were missing or wrong. The request is Rejected with Verification failed.

A failed check also shows its reason. Basic Auth says Credentials and API Key says API key where the others say Signature:

Reason What it means
Signature, Credentials or API key missing The request lacks a header the provider or method needs.
Signature, Credentials or API key invalid The header’s value is wrong or malformed, or the request repeats the header.

On Requests, the Status filter tracks processing stages. Its labels differ from the outcomes the list shows:

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

On Deliveries, the Outcome filter offers the outcomes above, with Pending · Queued and Pending · Sent as separate options.

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.