Know why it failed.

When a webhook delivery or a Send test fails, Settings > Webhooks now tells you why instead of showing only a status code.

Failed and timed-out rows in Recent deliveries end in a one-line reason, for example:

• Your endpoint answered with a redirect. Webhooks do not follow redirects, so use the URL that answers Subi directly.
• Your endpoint refused the request. If it checks the X-Subi-Hmac-Sha256 header, compare it as base64.
• No answer within the time limit, or Subi could not connect to your host.

Each delivery now also keeps the answer your endpoint sent back (the first 1,000 characters, plus the redirect location for a redirect), and the delivery details show it in a Response section. A test you send reports whether it was delivered and how long it took.

Failure reasons also show on older failed rows. The stored response body and redirect location are kept only for delivery attempts made from now on, so older rows show the status and reason but no response body or redirect location.