Skip to main content
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

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. 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.

​
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. 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.

​
On-demand 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. This is useful when you’ve made changes in an integrated system and want them reflected in C1 right away.

​
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.
See each connector’s documentation to check whether it supports continuous sync.

​
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 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, you can configure a custom sync schedule with a shorter interval (minimum 30 minutes).