Hirevire
Integrations

Webhook logs and delivery retries

The webhook logs show every delivery attempt for a job's webhook with its status and recorded error, and Hirevire retries failed deliveries automatically up to three attempts total. This reference covers where to find the logs, what each delivery status means, and the exact retry rules.

Open the webhook logs

Open the logs from the job's webhook settings, from a delivery-failure email, or from the command palette.

  • View logs — in the job's Settings → Webhook section. Opens the logs filtered to that job's webhook deliveries.

  • View the delivery logs — the link in the email Hirevire sends when a delivery fails. Opens the same filtered logs.

  • Go to Logs — from the command palette. Opens the general logs view.

The logs list the newest deliveries first and show 100 records per page. Filter with Select a job, Select date range, or All statuses, and use Reload logs to refresh.

Each delivery record stores the job and application it belongs to, the event type, the request URL, headers, and body that were sent, the response status and body, the delivery status, the attempt number, the creation and execution timestamps, and the error message when a delivery failed.

Delivery statuses

Each delivery has one of four statuses.

Status

Meaning

Pending

The delivery is queued and waiting to be sent.

Retrying

An attempt failed with a retryable error and the next attempt is scheduled.

Success

The delivery completed successfully.

Failed

The delivery ended without success and no more attempts are scheduled.

Retry schedule

Every delivery gets up to three attempts total.

  • Attempt 1: the initial delivery.

  • Attempt 2: sent 1 minute after the first retryable failure.

  • Attempt 3: sent 10 minutes after the second retryable failure.

The third attempt is final: if it succeeds the delivery is marked Success, and if it fails the delivery is marked Failed.

Which failures are retried

Only three failure types trigger a retry; any other HTTP error fails the delivery immediately.

  • Transport or network failure — the endpoint did not respond, recorded as status 0. A request that times out after 30 seconds is recorded with the message "Request timed out"; other transport failures record the transport error message.

  • HTTP 429 — the endpoint returned a 429 response, recorded with the message "HTTP 429".

  • HTTP 500 or higher — the endpoint returned a server error, recorded with the message "HTTP 500" or the corresponding status.

Any other HTTP status fails immediately and is not retried.

How deliveries are sent

Each delivery is a POST request with a JSON body that includes your configured request headers and any signing headers. Requests time out after 30 seconds, and a timeout counts as a retryable transport failure. The stored response body is truncated to the first 10,000 characters.

Webhook auto-disable

A webhook is automatically disabled after 5 consecutive terminal delivery failures.

Webhook status is separate from delivery status: the webhook itself is either Active or Disabled, while each delivery within it is Pending, Retrying, Success, or Failed.

When a webhook is disabled, the job's webhook settings show "This webhook was auto-disabled after repeated failures" with the date and time it was disabled, and a Re-enable button. The organization owner also receives an email with the subject "Hirevire: Webhook disabled for [Job Title]".

Fix the endpoint, then click Re-enable in the job's Settings → Webhook section. Re-enabling sets the webhook back to Active, clears the consecutive-failure count and the disabled timestamp, and confirms with "Webhook re-enabled."

Was this helpful?
Was this helpful?