> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trytikt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Delivery and retries

> What counts as delivered, when TIKT tries again, when it turns a destination off, and how nothing is lost.

## Delivered

A request is **delivered** when your endpoint answers with a `2xx` status within **15 seconds**, connection included.

* **Redirects are not followed.** A `3xx` answer counts as a failure: give TIKT the final address.
* The first **1 KB** of your answer is kept in the destination's log (**Recent deliveries**), to help you debug. The rest is read and dropped.
* Answer fast, then do the work. If your processing takes long, accept the request first and handle it in the background.

## Retries

Any answer other than `2xx` — or no answer — is tried again, up to **8 attempts over about 27 hours and 35 minutes**:

| Attempt | When |
| - | - |
| 1 | right away |
| 2 | 5 seconds later |
| 3 | 5 minutes later |
| 4 | 30 minutes later |
| 5 | 2 hours later |
| 6 | 5 hours later |
| 7 | 10 hours later |
| 8 | 10 hours later |

The times are approximate: TIKT checks for due deliveries every few minutes. After the eighth failure, the delivery is given up (**gave up** in the log); you can still [resend](#resend) it.

When a `429` or `503` answer carries a `Retry-After` header, TIKT waits at least that long (10 hours at most) before the next attempt.

Every attempt carries the same `webhook-id`: use it to ignore an event you already handled.

## A destination that keeps failing

TIKT **turns a destination off** when:

* it has failed for **3 days in a row** (no `2xx` since its first failure), or
* it answers **`410 Gone`**: TIKT takes it as “stop sending”.

The workspace owner gets an email, and your other destinations that listen to it receive [`webhook.endpoint_disabled`](/webhooks/events/destinations). **Nothing is lost:** the events keep piling up for it. Fix your endpoint, then turn the destination back on in **Settings › Integrations**: the events since its first failure are sent.

You can also turn a destination off yourself: nothing is sent and nothing is lost; turned back on, it catches up.

## Resend

Each row of **Recent deliveries** has a **Resend** button: TIKT sends the same message again — same `webhook-id` — with the objects **as they are now**. A resend adds a row to the log.

## Past events at creation

When you create a destination, you can ask for the events of the last **24 hours**, **7 days** or **31 days**: they are sent once, oldest first, right after the destination is created — as far back as TIKT keeps events, and no further back than **October 19, 2026**, when TIKT started recording them.

## How long TIKT keeps them

| What | Kept |
| - | - |
| Events (what can be sent, resent, or replayed when a destination is turned back on) | 180 days |
| The log of each destination (**Recent deliveries**) | 30 days |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.