Skip to main content
The sync task keeps integration-backed knowledge base content up to date by checking connected external sources and updating the synced content in Zylon when source content is added, changed, or removed. Use this task when you want content from SharePoint, Confluence, File System, Claromentis, or other supported integrations to stay fresh without manual resyncs.

​
Default configuration

By default, scheduled integration sync is disabled. When enabled, the default schedule is daily at 01:00. If timezone is not set, Zylon uses the server machine’s default timezone. 
integration:
  sync:
    enabled: false
    cron: "0 1 * * *"

​
Configuration example

Edit /etc/zylon/zylon-conf.yaml, then apply the change with sudo zylon-cli sync. 
integration:
  sync:
    enabled: true
    cron: "0 1 * * *"
    timezone: "Europe/Madrid"
enabled turns the scheduled sync on or off. cron defines when it runs, and timezone optionally defines which timezone is used to interpret that cron expression. If timezone is omitted, the server machine’s default timezone is used.
We suggest setting an IANA timezone that matches your company’s timezone.

​
Accepted cron and timezone values

​
Cron values

Cron schedules use a 5-part format: 
minute hour day-of-month month day-of-week
Use values in these ranges:
FieldAccepted values
Minute0-59 or *
Hour0-23 or *
Day of month1-31 or *
Month1-12 or *
Day of week0-6 or *
Examples:
  • 0 3 * * * runs every day at 03:00
  • 30 2 * * 1 runs every Monday at 02:30

​
Timezone values

integration.sync.timezone is optional. If it is not set, the sync cron runs in the server machine’s default timezone. When you set integration.sync.timezone, use a valid IANA timezone identifier. Common examples include:
  • UTC
  • Europe/Madrid
  • America/New_York
  • America/Los_Angeles
  • Asia/Tokyo
  • Pacific/Auckland
  • Africa/Johannesburg
For a practical list of IANA timezone identifiers, see IANA Time Zones.

​
Execution and failure handling

A scheduled sync run checks active integration content and may call external APIs, download content, create or remove synced knowledge base content, trigger ingestion, and emit sync completion messages. If one sync target fails, the error is logged and the task continues with other targets. The next scheduled run tries again.