Logs
See every Survey events delivery, what the tool answered, how retries work and how to send a failed delivery again
Overview
Logs lists every Survey events delivery to your tools, by its latest attempt. Use it to confirm a new connection works, to find out why a tool refused an event, and to send failed deliveries again once the cause is fixed.
Open it from Data sync → Logs.
Deliveries are kept for 15 days (7 days for deliveries made with test keys).
Reading the list
| Column | Meaning |
|---|---|
| Time | When the latest attempt was made, in the project's time zone. |
| Connection | The connection that sent it. A test carries a Test mark. |
| Event | Survey shown, started, submitted, partially submitted or dismissed. |
| Outcome | What happened to the delivery. See the table below. |
| Tool answer | The tool's status code and the start of its answer, for example 200 or 401. A delivery that waited for the rate limit says so, for example 200 · waited 59 s (rate limit). |
| Attempts | How many times Encatch tried. |
Click a row to open its details: the first try, the latest try, each attempt and the tool's answer.
Filters
Filter by Time (last hour, 6 hours, 24 hours, 7 days or 15 days), Connection, Outcome and Event. Hide tests leaves out Test connection sends. Refresh loads the latest deliveries.
Outcomes
| Outcome | What it means | What to do |
|---|---|---|
| Delivered | The tool accepted the event. | Nothing. |
| Will retry | The attempt failed in a way that may pass later: the tool was down, slow or answered with a rate limit. | Nothing. Encatch tries again by itself. |
| Failed | The tool refused the event, or every retry was used up. The details say which: Key refused, Refused by the tool, or Kept to send again. | Fix the cause (for example replace the key), then Send again. |
| Expired | The event waited longer than the connection's Maximum wait for a free minute under its rate limit. | Raise the rate limit or the maximum wait if it keeps happening, then Send again. |
| Skipped | Nothing was sent, on purpose: for example the user has no value for the chosen identifier, or the tool does not take the user. | Check Identify users by and its fallback in the connection's Advanced options. |
Retries
When an attempt fails in a way that may pass later, Encatch tries again after 1 minute, then 10 minutes, then 1 hour. The delivery shows as Will retry in between.
If the last retry fails too, the delivery ends as Failed and is kept so you can send it again.
A refused key is not retried: no later attempt can pass until the key is replaced.
A retry can reach a tool twice, for example when the tool accepted the event but its answer was lost. Where a repeat matters, use the response ID (or the event ID the automation tools get) to skip it.
Waiting to be sent
When deliveries are held back, a box above the list shows how many are waiting to be sent now, per connection. Deliveries wait for the connection's rate limit, or for a tool that is slow or failing. They join the list once they are sent.
Send again
Failed and expired deliveries that were kept can be sent again.
Fix the cause — For example paste a new key with Replace, switch the tool's webhook back on, or raise the rate limit.
Select the deliveries — Tick the rows that say can be sent again. You can send one, or up to 100 at once.
Click Send again — The deliveries are queued. Press Refresh to see their new outcome.
Tests, skipped deliveries and delivered ones cannot be sent again.
Troubleshooting
| What you see | Likely cause | What to do |
|---|---|---|
| No deliveries at all | The connection is not sending yet or is paused, the survey is not among the connection's surveys, or the event is not ticked | Open the connection: press Start sending or Resume, and check Surveys and What is sent |
| Only Survey submitted arrives | Shown, started and dismissed are sent for identified users only | Identify your users in the SDK |
| Nothing for anonymous respondents | Include anonymous respondents is off, or the tool does not take anonymous users | Turn it on in General, if the tool offers it |
| Skipped on every event | The users lack the chosen identifier and the fallback is Don't send | Change Identify users by or its fallback |
| Key refused | The key was deleted, rotated or mistyped | Paste the current key with Replace, then Send again |
| Delivered in Encatch, missing in the tool | The region is wrong, or the tool accepted the call and dropped the event | Check the region and the tool's own activity view. The connector page lists known cases |
Next steps
- Connection settings — rate limit, maximum wait and user identity
- Survey events — what each event means
Was this page helpful?
