Delivery logs
How to review third-party delivery attempts and outcomes.
Delivery Logs are the read-only operational trail for automatic and test third-party requests.
With Read Delivery Log, open Processing & Monitoring → Third Party Delivery → Delivery Logs. Filter by Company, system, entity, event, status, test flag, correlation ID, date, or search, then open a row.
The detail shows:
- destination URL and HTTP method;
- sanitized request headers and mapped request payload;
- HTTP response status and a protected representation of response headers and body;
- status, attempt/max attempts, duration, correlation and job IDs;
- failure message and next retry time.
Statuses are Pending, Success, Failed, and Retrying. Retries are driven by the delivery worker and the Hook or System retry policy.
New third-party response headers and bodies are encrypted before they are stored. Read Delivery Log does not reveal them. A user with the separate Decrypt Delivery Log permission can enable Decrypt response on the detail page; the server checks that permission independently and records the decrypt request as a synchronous high-sensitivity audit event. Turn decryption off when the diagnostic review is complete.
Historical response values created before response encryption are also hidden from ordinary reads and can be returned only through the same audited decrypt path.