Channel messages not delivered
Channel delivery problems usually involve webhook configuration, provider authentication, or response formatting. The worklog helps you determine whether the issue is on the inbound or outbound side.
Common causes
Section titled “Common causes”| Symptom | Likely cause |
|---|---|
| Inbound messages not received | Webhook URL is wrong, provider token expired, or signature verification failed. |
| Agent responds but user does not see it | Channel adapter failed to format or send the outbound message. |
| Duplicate responses | Webhook retries because the runtime did not acknowledge quickly enough. |
| Wrong user thread | Session or user mapping is inconsistent across messages. |
Diagnostic steps
Section titled “Diagnostic steps”-
Check the worklog for the conversation. Is the inbound message present? Is an outbound response generated?
-
Verify the provider webhook points to the runtime channel endpoint and is active.
-
Check provider credentials in the registry for expiration or revocation.
-
Review runtime logs for signature verification failures or adapter errors.
-
Confirm the response template renders valid output for the channel format.
-
Check session mapping to make sure repeat messages from the same sender are tied to the same conversation.
- Re-register the webhook URL and verify the endpoint is reachable from the provider.
- Rotate expired provider tokens and update the registry.
- Return HTTP 200 quickly to the provider to avoid retries, even if inference is still running.
- Simplify response templates if formatting errors are reported.
- Ensure sender identifiers are normalized consistently.