Suspended service

Discover the cause and solution for suspended service errors.

If you see the error message below when evaluating a query, fetching content, or tracking an event, the API returned an empty 202 Accepted response because personalization is paused for this request.

This is not an integration problem. The X-Suspension-Reason response header indicates which of the two causes applies:

  • Tracking and personalization suspended — the workspace has suspended its services, which you can resume anytime from the workspace settings.
  • Bot personalization blocked — the request was identified as bot traffic and skipped to keep your metrics clean. You also can change it from workspace settings.

In both cases, make sure your application defines fallback content so it degrades gracefully.