From 8531560d424a3ade29b651023b30d6bdf264bb53 Mon Sep 17 00:00:00 2001 From: Melinda Moreland Date: Mon, 21 Sep 2026 16:06:48 -0700 Subject: [PATCH] docs: note scope-narrowing as a common sync-pause trigger Connector setup fields that narrow sync scope (tenant/project/org filters) drop the excluded scope's grants when added to a connector that already synced more broadly, which trips C1's anomaly-detection pause. Call this out generally so connector-specific docs can link here instead of re-explaining it. Co-Authored-By: Claude Sonnet 5 --- baton/configure.mdx | 6 ++++-- baton/faq.mdx | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/baton/configure.mdx b/baton/configure.mdx index 2a11bd06..6f76d8b1 100644 --- a/baton/configure.mdx +++ b/baton/configure.mdx @@ -38,9 +38,11 @@ You can specify which attributes each connector syncs or ignores. This allows yo ## Connector sync pause -C1 automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next). +C1 automatically pauses a connector’s sync cycle and alerts the connector owner if significant data anomalies are detected (for example, if the number of resources decreases by half between one sync and the next, or if a large number of grants are removed). -When a significant drop in resources is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1 know that the change is expected and that it’s safe to proceed. +When a significant drop in resources or grants is detected during a connector sync, C1 does not immediately apply the change as a precaution against unintentionally removing access. A banner explaining that the sync has been paused is displayed. Click **Confirm changes** in the banner on the application’s page to let C1 know that the change is expected and that it’s safe to proceed. + +A common way to trigger this pause: adding a setup field that narrows what a connector syncs — for example, limiting it to specific tenants, projects, orgs, or sites — to a connector that already synced without that field set. Excluding scope that was previously synced also excludes the grants and memberships tied to it, which registers as a significant drop. This is expected; confirm the change to apply the narrower sync going forward. Check the connector’s own documentation for which setup fields can narrow its sync scope. ### Turn off connector sync pause diff --git a/baton/faq.mdx b/baton/faq.mdx index be813d51..0db04e2b 100644 --- a/baton/faq.mdx +++ b/baton/faq.mdx @@ -37,7 +37,7 @@ Syncing is a read-only operation. Most connectors use syncs that are scheduled t If a connector experiences three consecutive sync failures, an automated email alert is immediately dispatched to the designated owner, letting you take action quickly to correct the issue. -We’ll also automatically pause a connector’s sync cycle and alert you if significant data anomalies are detected (such as if the number of synced resources decreases by half between one sync and the next). This setting is on by default, but you can configure it by navigating to an app’s **Configure connector** > **Advanced** tab. +We’ll also automatically pause a connector’s sync cycle and alert you if significant data anomalies are detected (such as if the number of synced resources decreases by half between one sync and the next, or if a large number of grants are removed — for example, after narrowing a connector’s setup fields to sync a smaller scope than it previously synced). This setting is on by default, but you can configure it by navigating to an app’s **Configure connector** > **Advanced** tab. See [Connector sync pause](/baton/configure#connector-sync-pause) for details. ### Provisioning