Delivery Attempts
A Delivery Attempt is created each time an Event Channel subscription matches an Event Record and routes it to a Target. Delivery attempts are read-only audit rows that track the outcome and retry state for each individual delivery.
Because event delivery is asynchronous, a delivery attempt may appear a moment after its corresponding event record.
We retain delivery attempts for 30 days.
Statuses
| Status | Meaning |
|---|---|
| Queued | The delivery has not been attempted yet. |
| Success | The delivery completed successfully. |
| Retrying | A delivery attempt failed and will be retried automatically. |
| Failed | All retry attempts have been exhausted. The delivery did not succeed. |
Retry Policy
When a delivery fails, Files.com retries automatically. Each retry is tracked as a separate attempt. If all retries are exhausted without a successful delivery, the status moves to Failed.
Details Recorded in Delivery Attempts
Each delivery attempt record includes the following details.
| Column | Details |
|---|---|
| ID | Unique identifier for the delivery attempt. |
| Status | The current delivery status: Queued, Success, Retrying, or Failed. |
| Event Record | The event record this delivery attempt is for. |
| Event Target | The target this attempt delivered to, including target name and type. |
| Attempt Number | Which attempt this is in the retry sequence. |
| Response Code | The HTTP response code returned by the target, when applicable. |
| Error Message | Error details when the attempt failed. |
| Response Body | The response body returned by the target, when applicable. |
| Latency | How long the delivery attempt took. |
| Delivered At | When the delivery completed successfully. |
| Last Attempted At | When the most recent attempt was made. |
| Next Attempt At | When the next retry is scheduled, if the status is Retrying. |
| Created At | When the delivery attempt was created. |