Inspect and export integration history

Investigate missing tickets and delivery failures, find older attempts and export filtered history as CSV.

When a ticket is missing or an integration reports an error, inspect its history. It lists stored attempts with their outcome and, depending on the integration, requests, responses and error details.

Prerequisites

You need Integration Management permission. Deliveries require the relevant integration to be configured; an empty history does not confirm that an alert rule is set up correctly.

Find an attempt

Open Administration → Integrations and the affected integration. For webhooks, Teams or email, open the specific webhook, channel or recipient.
Open History or the displayed delivery table.
Enter a term in Search history… and press Enter. For example, search for a ticket number or error message present in the stored details. Searchable fields depend on the integration.
Narrow the results with Operation, Outcome, From and Through. Through includes the selected day. Search and filters cover all stored history, not only the visible page.
Sort using a sortable column header or page through the results below. The default is newest attempts first and 50 rows per page; you can choose 25, 50, 100 or 200.
Expand the relevant row. Read the available request and response data, error details and, where shown, the next retry time.

Reset filters clears the search and filter conditions. An empty filtered list only means no stored entry matches those conditions.

Interpret the outcome

Outcome or symptom	Next action
Skipped or Not configured	Read the reason. Check, for example, customer mapping, the connection and the selected alert channel.
Failed	Inspect the status code and response. Correct credentials, permissions or invalid values; note any next retry already scheduled.
Dead-lettered	No further automatic retries are scheduled for this attempt. Resolve the cause and check whether the channel offers manual replay.
Successful, but the expected ticket is missing	Use the ticket ID or number in the response and check the customer and destination system. A successful delivery attempt alone does not confirm every downstream action in that system.
No response recorded	Read any available error details. A missing response does not prove that the destination processed nothing.

For connection errors or timeouts, also check the firewall or IP allowlist in front of the API or receiver. See IP addresses and firewall rules; a successful connection from your browser does not confirm reachability from octoja.

For webhooks, the delivery chart covers the last 24 hours. It is not limited to the visible table page, so its count need not match a history with different filters.

Export filtered history

Set the desired search, filters and sorting.
Open the table's … menu and choose Export CSV.
Use the file for further analysis or sharing. It includes all matching rows, not only the current page. Attempts arriving after export starts are excluded.

Warning: History and exports can contain customer, device and error data. Review the content before sharing it outside your team.

Replay a delivery

Replay is available for webhooks, Teams, email and Woasi, not every integration. Expand the relevant row and use the button only after resolving the cause. The connection must still be usable.

A replay can trigger another action in the destination system. First check whether the original delivery was already processed there, especially after a timeout.

Was this helpful?

Still need help? Ask the team