Rollout and rollback

Enable one vertical at a time in a non-production environment:

PUBLIC_API_V1_ENABLED=true
PUBLIC_AGENT_DISCOVERY_ENABLED=true
KNOWLEDGE_LISTS_ENABLED=false
KNOWLEDGE_SYNC_ENABLED=false
NATIVE_BOOKING_ENABLED=false
NATIVE_SUBSCRIBERS_ENABLED=false
NATIVE_CALLBACKS_ENABLED=false
NATIVE_CHAT_ENABLED=false
SURVEYS_ENABLED=false
AGENT_FORM_SUBMISSIONS_ENABLED=false
MCP_ENABLED=false
A2A_ENABLED=false

Order

Deploy additive migrations and API v1.
Verify UUID backfills, tenant isolation, legacy embeds, and Page rendering.
Enable public discovery and validate HTML, Markdown, manifest, sitemap, and Agent Card parity.
Enable each engagement feature for internal canary workspaces. Enable surveys after testing dashboard publishing, public responses, and SMS/WhatsApp distribution preflight for a tenant. Enable agent form submissions only after testing a simple form and its OTP confirmation.
Enable MCP, then A2A, only after authentication and confirmation smoke tests.
Enable knowledge sync provider-by-provider.

Rollback

Disable the affected flag and clear config cache. Do not reverse a migration while newer application code may still write to it. Keep the additive schema through the observation period, then remove it in a later reviewed release only if the pivot is abandoned. Agent traces are sampled at 100% only when SENTRY_AGENT_MONITORING_ENABLED=true. Prompt and model-output capture is not implemented; enabling it requires a separate privacy approval.

Get started

Build

Operate

Order

Rollback

​Order

​Rollback

Order

Rollback