Skip to main content

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

StatusMeaning
QueuedThe delivery has not been attempted yet.
SuccessThe delivery completed successfully.
RetryingA delivery attempt failed and will be retried automatically.
FailedAll 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.

ColumnDetails
IDUnique identifier for the delivery attempt.
StatusThe current delivery status: Queued, Success, Retrying, or Failed.
Event RecordThe event record this delivery attempt is for.
Event TargetThe target this attempt delivered to, including target name and type.
Attempt NumberWhich attempt this is in the retry sequence.
Response CodeThe HTTP response code returned by the target, when applicable.
Error MessageError details when the attempt failed.
Response BodyThe response body returned by the target, when applicable.
LatencyHow long the delivery attempt took.
Delivered AtWhen the delivery completed successfully.
Last Attempted AtWhen the most recent attempt was made.
Next Attempt AtWhen the next retry is scheduled, if the status is Retrying.
Created AtWhen the delivery attempt was created.