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.
Site Administrators see delivery attempts across all workspaces. Workspace Administrators see only delivery attempts from their own workspace.
Delivery attempt records are retained for 30 days from creation, or until their associated event record is removed, whichever comes first. Their removal does not undo a completed delivery or remove the channel, subscription, or target configuration.
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 updates the same delivery attempt record, including its attempt number and next retry time. If all retries are exhausted without a successful delivery, the status moves to Failed.
Subfolder Summary Delivery
When a Slack or Teams target uses Subfolder Summaries, each contributing event retains its own delivery attempt. Those attempts remain Queued while activity is being collected and share a Summary ID. Sending one summary updates every contributing attempt with the same delivery result and retry schedule, so several Success rows with the same Summary ID describe one message rather than separate messages for each event.
If delivery fails, the summary is retried with the same counts; later activity starts another summary. Relevant configuration changes discard pending summaries and mark their contributing delivery attempts 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 Subscription | The subscription that matched the event and triggered this delivery attempt. |
| Event Target | The target this attempt delivered to, including target name and type. |
| Attempt Number | Which attempt this is in the retry sequence. |
| Summary ID | Identifies the Slack or Teams subfolder summary this event contributes to, when applicable. |
| 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. |