For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Go to app
DocumentationAPI Reference
DocumentationAPI Reference
  • API Reference
    • Introduction
    • Users
    • Taskflow
    • AI Task Builder
    • Studies
    • Representative sample studies
    • study-collections
    • Filter Sets
    • Participant Groups
    • Custom Groups
    • Study Distribution
    • Submissions
    • Bonuses
    • Messages
    • Workspaces
    • Projects
    • Surveys
    • Webhooks
      • Subscribing
      • Receiving
      • Event Delivery and Retry Logic
      • Persistent Failures and Disabling Logic
      • Idempotency and the X-Event-ID Header
      • Handling event order with X-Timestamp
      • Verifying
      • GETList all subscribable event types
      • GETList all secrets
      • POSTCreate/replace a secret
      • GETList all subscriptions
      • POSTCreate a subscription
      • GETRetrieve a subscription
      • POSTConfirm a subscription
      • DELDelete a subscription
      • PATCHUpdate a subscription
      • GETGet subscription events
    • Invitations
    • Reward Recommendations
    • Testing
    • Well Known Endpoints
Go to app
LogoLogo
On this page
  • When We Detect Ongoing Failures
  • What Happens Next
  • Summary
API ReferenceWebhooks

Persistent Failures & Disabling Logic

|View as Markdown|Open in Claude|
Was this page helpful?
Previous

Event Delivery and Retry Logic

Next

Idempotency and the X-Event-ID Header

To protect your systems and ensure transparency, we actively monitor delivery health.

When We Detect Ongoing Failures

If all webhook deliveries for a given Target URL and Event Type are failing (100% failure rate) for 5 consecutive days, we consider this a persistent failure.

What Happens Next

  • Day 3: Our Customer Success team will reach out to notify you of the issue and offer support.
  • Day 5: If failures continue, we will automatically disable the affected Target URL + Event Type to prevent further disruption.
This policy ensures a balance between reliability and control. You will be notified before any automatic disabling action is taken.

If your service is back online or the issue has been resolved, you can re-enable the endpoint or reconfigure your webhook settings via the dashboard or API.

Summary

  • Up to 12 delivery attempts over 24 hours
  • Full jitter to avoid retry spikes
  • Monitored failure rates by Target URL + Event Type
  • Transparent escalation with proactive communication
  • Automatic protection against long-term failures