Troubleshooting
Find out why a request failed or a message didn't arrive.
A request failed
Check the HTTP status and the response's code and message.
| Status | What to check |
|---|---|
401 | Use a valid, active workspace API token. |
404 | Check that the channel or project exists and its name matches exactly. |
409 | Reuse the original content for that idempotency key. |
429 | The custom Messages API request limit was reached; honor Retry-After. |
503 or a network timeout | Retry with the same key and content. |
See the API reference for all response statuses.
No messages from an integration
Check that the connection is active and the provider has the right webhook URL and secret, if required.
Then check the provider's event settings:
- Sentry: Match Issue Category to Error or Feedback.
- RevenueCat: Include Renewal for trial conversions.
- Vercel: Only production deployments are forwarded.
- AWS SNS: The subscription must be Confirmed, its Topic ARN must match, and raw message delivery must be off.
Repeated alerts
Matching Sentry issues and Dokploy server alerts stay quiet for 60 minutes after the first alert.
A message is in its channel but not in Inbox
Open the channel and click Subscribe. Its history will appear in your Inbox; only new messages trigger push.
No phone notification
- Install appkeepr and sign in with the same account and workspace.
- Subscribe to the channel before sending a new message.
- Enable notifications in appkeepr and your phone's settings. Check Focus and Do Not Disturb too.
- Make sure your phone is online, then send a fresh test message.
Messages and push are separate
API success means your message is in the channel. Push gets one sending attempt; failed sends aren't retried. You can still read the message in Inbox.