Update Sync Policy
Sets a source’s sync schedule, replacing the previous one, and returns it.
Saving does not start a sync. The first scheduled sync is due one interval after the update, and each later one an interval after the previous one was queued. To sync now, call Sync Source.
After each import into the source finishes, save the schedule again with the source’s new version. An import changes version, and a schedule still bound to the old one turns itself off at its next due time.
To pause scheduled syncs without changing the schedule, set the source’s status to disabled with Update Source. A sync that came due meanwhile runs when the source is set back to active.
For the read-then-save flow, see Sync and Schedule Sources.
Authorization
Path parameters
…/knowledge-fs/spaces/<knowledge base ID>), and the segment after /datasets/new/ in the address bar.Body
application/jsonmode: custom and rejected with the other modes.Range: 3600–2592000
false with mode: manual.revision, from Get Sync Policy. Send 0 when the source has no schedule yet. The revision also increases every time a scheduled sync starts, so read it right before updating. A stale value answers 409 and nothing changes.Range: >= 0
version, from Get Source or List Sources. It changes after every Update Source call and every completed import, so read it right before updating. A stale value answers 409 and nothing changes.Range: >= 1
manual turns scheduled syncs off, interval syncs every 24 hours, and custom syncs every customIntervalSeconds.manualintervalcustomResponses
mode: manual or enabled: false, next_run_at is null.mode: custom. null for the other modes.false with mode: manual.version the schedule is bound to.manual (no schedule), interval (every 24 hours), or custom (every custom_interval_seconds).null when nothing is scheduled.expectedRevision on Update Sync Policy. It increases on every update and every time a scheduled sync starts.