> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stoneturner.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Sync Scheduling & Retries

> How Stoneturner schedules incremental syncs and retries failed pipeline steps.

Stoneturner runs background jobs to keep your synced data up to date and recover from transient failures.

<Note>
  If self-hosting, set `CRON_ENABLED=false` in `.env` to disable all three cron jobs. Manual sync and retry endpoints still work.
</Note>

## Sync schedules

Each integration can have its own sync frequency. Configure it from the knowledge base UI — open the **Sync frequency** dialog (`sync-schedule-dialog.tsx`) and choose **Daily**, **Weekly**, **Monthly**, or **No Schedule**.

<img src="https://mintcdn.com/stoneturner/zoN3D-djL0a_fh1E/assets/sync-schedule.png?fit=max&auto=format&n=zoN3D-djL0a_fh1E&q=85&s=148c43cf1e0d056a6bf2af1af5423033" alt="integrations" style={{borderRadius: "10px"}} width="1316" height="664" data-path="assets/sync-schedule.png" />

## Retries

When a pipeline step fails, it writes a `syncTask` row with `status: "FAILED"`, the `step` name, and `inputs` (cursor, offset, or other resume state).

These steps are retried once per day until they reach a `SUCCESS` state OR have 3 `FAILED` attempts in a row.

### Manual trigger

If you'd like to trigger a retry immediately, you can manually triggers the retry for all failed tasks in the UI.

<img src="https://mintcdn.com/stoneturner/zoN3D-djL0a_fh1E/assets/manual-retry.png?fit=max&auto=format&n=zoN3D-djL0a_fh1E&q=85&s=bfbec864f439b2a5b07466c755c67e9c" alt="integrations" style={{borderRadius: "10px"}} width="1768" height="452" data-path="assets/manual-retry.png" />

## Common questions

<AccordionGroup>
  <Accordion title="What if I don't want automatic syncing?">
    Select **No Schedule** in the sync frequency dialog. Stoneturner removes that integration's `syncPipeline` row, so the midnight scheduler ignores it. You can still trigger syncs manually.
  </Accordion>

  <Accordion title="Can I run a sync immediately?">
    Yes. Use the per-integration sync button in the UI, which calls `POST /api/sync/:integration` for a full sync. For an incremental sync only, use `POST /api/sync/updates/:integration`.
  </Accordion>

  <Accordion title="How do I know if retries are failing?">
    Check the server console. `retry-cron.ts` logs each failed retry with the integration, step name, task ID, and error message.
  </Accordion>

  <Accordion title="What happens to integrations I disconnect?">
    Deleting an integration's credential calls `DELETE /api/sync/:integration`, which invokes that integration's `deleteSync` implementation. This removes its pipeline row, purges artifacts and embeddings, and clears integration-specific data.
  </Accordion>
</AccordionGroup>

<Tip>
  For a deeper look at how sync steps record progress and resume state, see [Add integrations](/add-integrations) and the [architecture](/architecture) page.
</Tip>