Scheduled jobs
Describes the scheduled jobs related to syncing content from CMS (SaaS) to Optimizely Graph.
Changes to content and content types in Optimizely Content Management System (CMS) (SaaS) are automatically synched to Optimizely Graph. However, CMS (SaaS) includes two scheduled jobs to handle some special cases.
To access the scheduled jobs, go to Settings > Scheduled Jobs. Click Start for the type of scheduled job you want to run.
Optimizely Graph full sync
This job is not set up to run in a scheduled manner. It can, however, be executed manually if needed. When run, it will do a full synchronization and sync all content types and all content instances, so it can take some time to execute depending on how many content instances CMS (SaaS) contains.
To ensure existing indexed items are removed before synchronizing, you can optionally reset the Optimizely Graph account before running the full sync job. Optimizely Graph or Admin in the CMS (SaaS) UI menu.
![Optimizely Graph Full Sync](https://files.readme.io/e92f478-image.png)
Use cases for full sync
Used to handle when configuration changes such as:
- If the site is re-configured, for example, when hosts are changed.
- Take advantage of a new feature requiring additional data to be indexed.
Optimizely Graph delta sync
The Optimizely Graph Delta Synchronization job is configured to run once every hour by default. When it executes, it queries CMS (SaaS) for content and content type changes that have occurred since the last execution and then resyncs those changes. The job runs automatically so that if a temporary outage occurs, the Optimizely Graph index should catch up with changes afterward.
![Optimizely graph delta sync](https://files.readme.io/69ce102-image.png)
Use cases for delta sync
Used to handle temporary outages such as:
- When the Optimizely Graph service is unavailable.
- When the CMS (SaaS) application is shut down (for example, due to down-scaling) during a sync.
Updated about 2 months ago