Skip to main content
Intramedial
AS

Read-only demo account · Enterprise

The Awesome Company, Inc.

All capabilities enabled · unlimited quotas · 42 active agents · 4 workspaces

Support · Ticket

Ticket detail

Thread · attached grants · audit-log cross-reference · signed receipt. Resolution requires your confirmation.

Back to inbox
High· State: In progress· integrationID tkt_demo_001

Webhook deliveries failing intermittently

Opened 5 hours ago · Last update 30 minutes ago · Agent did:web:intramedial.com:staff:alice

Access grants on this ticket

What the agent can see while this ticket is open. Revoke any of these any time.

  • Diagnose webhook delivery failures to hooks.example.com· active· only alice
    • · Audit log · read only · last 7d (read)
    • · Webhooks · read configuration only (read)

    Expires in 3 days · 12/200 reqs used

Conversation

Every internal note is visible — no backstage (per audit policy 40 §2).

Live chat unavailable — replies persist in the ticket
  • You5 hours ago

    Webhook deliveries to hooks.example.com return 503 every ~30 min. The target is healthy when I poll it from my laptop. Need help diagnosing.

  • AI assistant AI · claude opus5 hours ago

    Triaged — this looks like a known intermittent failure pattern on `hooks.example.com` due to their rate limiter. I'm escalating to a human teammate (Alice) who can verify against your delivery log + propose a fix. Estimated first response: <2h.

  • alice1 hour ago

    Hi Michele — Alice from Tier 1 here. I've reviewed the delivery log via the grant you attached. Confirmed: the target's rate limiter trips around the 5-req-per-minute mark which matches your event volume during the 30-min spikes. Two paths: (1) configure auto-retry with longer backoff, (2) install a buffer queue on your side. I can propose the first as a config change here in the workbench if you want.

Plaintext (KEK-wrapped at rest)

Audit log cross-reference

Every state transition + access read on this ticket is in your workspace audit log.

Open audit log for this ticket

Receipt chain: 4 signed steps · OTS anchor Pending