From 6deffcc7db582d100694e3a6ce9a87a1caa248d9 Mon Sep 17 00:00:00 2001 From: "c1-dev-bot[bot]" <2740113+c1-dev-bot[bot]@users.noreply.github.com> Date: Thu, 4 Jun 2026 16:57:44 +0000 Subject: [PATCH 1/3] Add default sync schedule documentation to connector FAQ Adds detailed sync schedule information to the connector FAQ page: - Default sync intervals (1 hour with access requests, 24 hours otherwise) - Custom sync schedule options (fixed interval and cron) - On-demand sync availability - Continuous sync explanation Fixes: DAT-644 --- baton/faq.mdx | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) diff --git a/baton/faq.mdx b/baton/faq.mdx index 68d08f34..7e87955a 100644 --- a/baton/faq.mdx +++ b/baton/faq.mdx @@ -33,6 +33,34 @@ Specifically, C1 syncs: Syncing is a read-only operation. Most connectors use syncs that are scheduled to run at regular intervals. Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next iteration of a set schedule. You can also start a sync on demand on any connector’s integration page. +#### Default sync schedule + +C1 automatically syncs each connector on a recurring schedule. The default interval depends on your tenant configuration: + +- **Tenants with access requests enabled:** Connectors sync every **1 hour** by default. +- **All other tenants:** Connectors sync every **24 hours** by default. + +These defaults apply when no custom sync schedule has been configured for the connector. + +#### Custom sync schedules + +You can configure a custom sync schedule for individual connectors. Custom schedules support two formats: + +- **Fixed interval:** Set a specific duration between syncs (for example, every 6 hours). The minimum configurable interval is 30 minutes. +- **Cron schedule:** Use a cron expression with timezone support for more precise scheduling (for example, daily at midnight in a specific timezone). + +Some connector types enforce a minimum sync interval that overrides shorter custom schedules to protect the external system from excessive API calls. + +#### On-demand sync + +You can start a sync at any time from the connector’s integration page in C1, regardless of the configured schedule. There is a short cooldown period between on-demand syncs to prevent overlapping operations. + +#### Continuous sync + +Some connectors support continuous sync, which supplements the scheduled sync cycle. Instead of waiting for the next scheduled sync, continuous sync listens for change events from the external system and pulls new data as it becomes available. This reduces the delay between a change occurring in the external system and that change being reflected in C1. + +Continuous sync works alongside scheduled syncs — it does not replace them. Scheduled syncs still run at their configured interval to ensure a complete, consistent view of the external system’s data. + ### Sync issue or failure notifications 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. @@ -98,6 +126,17 @@ To learn more about configuring ticketing, check out [External ticketing](/produ Connectors periodically check in with C1 to request work. When tasks are available, any idle instance can claim the next task. This creates a worker-queue architecture: if one connector instance goes down, the remaining instances will pick up subsequent tasks. Note that only one sync task runs at a time per connector, and if an instance processing a task becomes unavailable, there may be a short delay (up to a few minutes) before the task is released and becomes available for another instance to claim. + + C1 automatically syncs each connector on a recurring schedule. The default sync interval depends on your tenant configuration: + + - **Tenants with access requests enabled:** Every **1 hour**. + - **All other tenants:** Every **24 hours**. + + You can customize the sync schedule for individual connectors by setting a fixed interval (minimum 30 minutes) or a cron expression with timezone support. Some connector types enforce a minimum interval that overrides shorter custom schedules. You can also trigger a sync on demand at any time from the connector's integration page. + + Connectors that support **continuous sync** supplement the scheduled cycle by listening for change events from the external system in near real-time, reducing the delay between changes and their reflection in C1. Continuous sync works alongside scheduled syncs and does not replace them. + + The relevant file is `sync.c1z`. By default, the connector stores this in a temporary folder determined by the host operating system (the location varies). You can specify a custom location for the `sync.c1z` file using a command-line flag. For example, in a Docker setup, you can map a volume to the container and specify a path to store the file. The `sync.c1z` file will then be stored in that mapped location. From ad46003fa5e69a667bf8e4c39706766122d56aff Mon Sep 17 00:00:00 2001 From: "c1-dev-bot[bot]" <2740113+c1-dev-bot[bot]@users.noreply.github.com> Date: Thu, 4 Jun 2026 17:02:45 +0000 Subject: [PATCH 2/3] Add sync schedule documentation for connectors Adds a dedicated sync schedule page covering default intervals (24h), continuous sync, on-demand sync, and audit considerations. Updates the FAQ syncing section with the default interval and a cross-reference. Fixes: DAT-644 --- baton/faq.mdx | 4 ++- baton/sync-schedule.mdx | 58 +++++++++++++++++++++++++++++++++++++++++ docs.json | 3 ++- 3 files changed, 63 insertions(+), 2 deletions(-) create mode 100644 baton/sync-schedule.mdx diff --git a/baton/faq.mdx b/baton/faq.mdx index 7e87955a..876ffe53 100644 --- a/baton/faq.mdx +++ b/baton/faq.mdx @@ -31,7 +31,9 @@ Specifically, C1 syncs: - **Accounts**, or the user accounts within the integrated system. - **Resources**, or the specific pieces of access (such as group membership or role assignment) in the integrated system and which accounts they’re assigned to. -Syncing is a read-only operation. Most connectors use syncs that are scheduled to run at regular intervals. Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next iteration of a set schedule. You can also start a sync on demand on any connector’s integration page. +Syncing is a read-only operation. By default, connectors sync every **24 hours**. Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next scheduled sync. You can also start a sync on demand on any connector’s integration page. + +For details on sync intervals, continuous sync, on-demand sync, and audit considerations, see [Sync schedule](/baton/sync-schedule). #### Default sync schedule diff --git a/baton/sync-schedule.mdx b/baton/sync-schedule.mdx new file mode 100644 index 00000000..854da267 --- /dev/null +++ b/baton/sync-schedule.mdx @@ -0,0 +1,58 @@ +--- +title: "Sync schedule" +sidebarTitle: "Sync schedule" +description: "Learn about default sync intervals, continuous sync, on-demand sync, and how sync scheduling works in C1." +--- + +C1 connectors periodically sync data from your integrated systems to keep your access records up to date. This page explains how sync scheduling works, including default intervals, continuous sync, and on-demand options. + +## Default sync schedule + +By default, connectors sync every **24 hours**. This means that once a connector is set up and running, C1 automatically retrieves the latest access data from the integrated system approximately once per day. + +Some connectors may have different default intervals based on the requirements of the integrated system. For example, connectors for systems with strict API rate limits may have longer minimum sync intervals to avoid exceeding those limits. + +## Sync scheduling types + +C1 supports three ways to schedule syncs: + +### Interval-based sync (default) + +Most connectors use interval-based syncing, where a full sync runs at regular intervals. After each sync completes, the next sync is automatically scheduled based on the configured interval. + +- The default interval is **24 hours**. +- Some connectors enforce a **minimum interval** based on the integrated system's API limits. If you configure a custom interval below this minimum, C1 automatically raises it to meet the requirement. +- Custom intervals that exceed the connector's minimum are preserved as configured. + +### Continuous sync + +Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next scheduled sync. Continuous sync uses event feeds or change detection to identify and retrieve only the data that has changed since the last sync. + +Continuous sync is useful for systems where near-real-time data accuracy is important, such as tracking admin events or audit logs. See each connector's documentation to check whether it supports continuous sync. + + + Even with continuous sync enabled, periodic full syncs still occur to ensure complete data consistency. + + +### On-demand sync + +You can manually trigger a sync at any time from the connector's integration page in C1. On-demand syncs run a full sync immediately, regardless of the regular schedule. This is useful when you've made changes in an integrated system and want them reflected in C1 right away. + +## Sync failure notifications + +If a connector experiences **three consecutive sync failures**, C1 sends an automated email alert to the designated application owner so you can investigate and correct the issue. + +C1 also automatically **pauses a connector's sync cycle** and alerts you if significant data anomalies are detected, such as the number of synced resources decreasing by half between consecutive syncs. This safety mechanism is enabled by default and can be configured by navigating to an app's **Configure connector** > **Advanced** tab. + +## Pausing and resuming sync + +You can pause a connector's sync schedule from the connector's configuration page. While paused, no automatic syncs run, but you can still trigger on-demand syncs. Resume the schedule at any time to return to automatic syncing. + +## Audit considerations + +For audit purposes, keep the following in mind: + +- The default sync interval of 24 hours means that access data in C1 may be up to 24 hours behind the source system. +- You can trigger an on-demand sync before generating audit reports to ensure the most current data. +- Sync history and status are available on each connector's integration page, providing a record of when syncs occurred and whether they completed successfully. +- If your audit requirements call for more frequent syncs, contact your C1 representative to discuss available options. diff --git a/docs.json b/docs.json index ae7426d1..44a51a93 100644 --- a/docs.json +++ b/docs.json @@ -333,7 +333,8 @@ "group": "Manage connectors", "pages": [ "baton/configure", - "baton/manage-connector" + "baton/manage-connector", + "baton/sync-schedule" ] }, { From 7ece3a1c87e47dc8b22d86b7c39d78739e3c5f7b Mon Sep 17 00:00:00 2001 From: "c1-dev-bot[bot]" <2740113+c1-dev-bot[bot]@users.noreply.github.com> Date: Thu, 4 Jun 2026 17:03:42 +0000 Subject: [PATCH 3/3] Update sync schedule page with tenant-specific defaults Aligns the dedicated sync schedule page with the expanded FAQ content, including 1-hour default for access request tenants, custom cron schedules, and 30-minute minimum interval. Fixes: DAT-644 --- baton/sync-schedule.mdx | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-) diff --git a/baton/sync-schedule.mdx b/baton/sync-schedule.mdx index 854da267..1cde6619 100644 --- a/baton/sync-schedule.mdx +++ b/baton/sync-schedule.mdx @@ -8,35 +8,37 @@ C1 connectors periodically sync data from your integrated systems to keep your a ## Default sync schedule -By default, connectors sync every **24 hours**. This means that once a connector is set up and running, C1 automatically retrieves the latest access data from the integrated system approximately once per day. +C1 automatically syncs each connector on a recurring schedule. The default interval depends on your tenant configuration: -Some connectors may have different default intervals based on the requirements of the integrated system. For example, connectors for systems with strict API rate limits may have longer minimum sync intervals to avoid exceeding those limits. +- **Tenants with access requests enabled:** Connectors sync every **1 hour** by default. +- **All other tenants:** Connectors sync every **24 hours** by default. -## Sync scheduling types +These defaults apply when no custom sync schedule has been configured for the connector. Some connectors may have different minimum intervals based on the requirements of the integrated system. For example, connectors for systems with strict API rate limits may have longer minimum sync intervals to avoid exceeding those limits. -C1 supports three ways to schedule syncs: +## Custom sync schedules -### Interval-based sync (default) +You can configure a custom sync schedule for individual connectors. Custom schedules support two formats: -Most connectors use interval-based syncing, where a full sync runs at regular intervals. After each sync completes, the next sync is automatically scheduled based on the configured interval. +- **Fixed interval:** Set a specific duration between syncs (for example, every 6 hours). The minimum configurable interval is **30 minutes**. +- **Cron schedule:** Use a cron expression with timezone support for more precise scheduling (for example, daily at midnight in a specific timezone). -- The default interval is **24 hours**. -- Some connectors enforce a **minimum interval** based on the integrated system's API limits. If you configure a custom interval below this minimum, C1 automatically raises it to meet the requirement. -- Custom intervals that exceed the connector's minimum are preserved as configured. +Some connector types enforce a **minimum sync interval** that overrides shorter custom schedules to protect the external system from excessive API calls. If you configure a custom interval below this minimum, C1 automatically raises it to meet the requirement. Custom intervals that exceed the connector's minimum are preserved as configured. -### Continuous sync +## On-demand sync -Some connectors support **continuous sync**, which pulls new data as it becomes available rather than waiting for the next scheduled sync. Continuous sync uses event feeds or change detection to identify and retrieve only the data that has changed since the last sync. +You can start a sync at any time from the connector's integration page in C1, regardless of the configured schedule. On-demand syncs run a full sync immediately. There is a short cooldown period between on-demand syncs to prevent overlapping operations. -Continuous sync is useful for systems where near-real-time data accuracy is important, such as tracking admin events or audit logs. See each connector's documentation to check whether it supports continuous sync. +This is useful when you've made changes in an integrated system and want them reflected in C1 right away. - - Even with continuous sync enabled, periodic full syncs still occur to ensure complete data consistency. - +## Continuous sync + +Some connectors support **continuous sync**, which supplements the scheduled sync cycle. Instead of waiting for the next scheduled sync, continuous sync listens for change events from the external system and pulls new data as it becomes available. This reduces the delay between a change occurring in the external system and that change being reflected in C1. -### On-demand sync +Continuous sync works alongside scheduled syncs -- it does not replace them. Scheduled syncs still run at their configured interval to ensure a complete, consistent view of the external system's data. -You can manually trigger a sync at any time from the connector's integration page in C1. On-demand syncs run a full sync immediately, regardless of the regular schedule. This is useful when you've made changes in an integrated system and want them reflected in C1 right away. + + See each connector's documentation to check whether it supports continuous sync. + ## Sync failure notifications @@ -52,7 +54,7 @@ You can pause a connector's sync schedule from the connector's configuration pag For audit purposes, keep the following in mind: -- The default sync interval of 24 hours means that access data in C1 may be up to 24 hours behind the source system. +- The default sync interval means that access data in C1 may be up to 1 hour (for tenants with access requests) or 24 hours behind the source system. - You can trigger an on-demand sync before generating audit reports to ensure the most current data. - Sync history and status are available on each connector's integration page, providing a record of when syncs occurred and whether they completed successfully. -- If your audit requirements call for more frequent syncs, contact your C1 representative to discuss available options. +- If your audit requirements call for more frequent syncs, you can configure a custom sync schedule with a shorter interval (minimum 30 minutes).