Agent Inbox items aren’t being delivered
Agent Inbox routes work items from Dailybot into your automation stack. When delivery stops, the webhook path, feature toggles, or rate limits are the usual suspects. Confirm each layer independently so you do not chase a client bug when the server never enqueued the event.
Quick check
- Webhook URL — Copy the configured endpoint from Dailybot and hit it with a signed test payload using your standard tool (curl, Postman) if policy allows.
- Inbox enabled — Verify the Inbox feature is on for the org and the specific workflow or agent feed you expect.
- Auth headers — Shared secrets, HMAC signatures, and bearer tokens must match what your receiver validates.
- Receiver logs — Check your HTTP service for 4xx/5xx responses Dailybot would interpret as failure.
- Rate limits — Burst events from large teams can trip either side’s throttles.
Common causes and fixes
Webhook misconfigured
Typos in URL, wrong path, or HTTP vs HTTPS mismatch cause immediate failures. Rotate to a known-good staging endpoint first, then swap back to production after you see 200 responses in Dailybot delivery logs (if exposed in UI) or your gateway. Ensure redirects are allowed or disabled; some clients do not follow POST redirects.
Inbox disabled
Feature flags, billing changes, or accidental toggles turn off Inbox without deleting configuration. Admins should open Agent Inbox settings, confirm the master switch, per-workflow switches, and that the source agent or check-in still publishes into Inbox.
Rate limiting
Dailybot may backoff when your endpoint returns 429, or your endpoint may drop when Dailybot sends a spike. Implement fast 200 acknowledgements and queue work asynchronously. Increase receiver concurrency or ask support about enterprise throughput if you routinely burst thousands of events.
SSL or network middleboxes
Corporate gateways that terminate TLS with custom CAs can break Dailybot’s outbound calls unless those CAs are trusted on Dailybot’s side (not configurable by you). Symmetrically, if your receiver uses a self-signed cert, Dailybot will refuse the connection. Use a publicly trusted certificate on your endpoint or a tunnel with valid certs for testing.
Payload schema drift
If you upgraded your receiver to expect new fields while Dailybot still sends the older schema (or vice versa), validation errors discard messages. Compare current documentation in Agent Inbox webhooks with your parser. Log raw bodies temporarily in a secure environment to diff.
If none of this worked
Before contacting support, gather:
- Organization name and workflow or inbox name
- Webhook URL host (not the secret path tokens if sensitive)
- HTTP status codes your server returned around the failure window
- Whether test deliveries from Dailybot UI (if available) succeed
- Approximate start time and timezone
- Steps you already tried from this article
Then contact Dailybot support from the Help or Contact options in the product or on the website.