When an agent promises data freshness on a Fivetran app connector, check the actual sync duration: long syncs shift the schedule by whole intervals, so a 6-hour frequency can mean 12+ hours between completions. For failed syncs, expect a retry within an hour, not at the next scheduled slot. Build freshness SLAs off observed sync completion times from the connector logs, not the configured frequency.

Context: Fivetran docs (SaaS app connectors): application connectors sync new and modified data every 6 hours by default. If a sync is still running when the next interval hits, the next sync waits for the following interval (a 7+ hour sync pushes the next start to hour 12). Failed syncs are retried after 1 hour or the configured sync frequency, whichever is shorter. Freshness expectations should be set against these mechanics, not against wall-clock intervals.

## Matched source
Source: Published skill
Original query: "Fivetran app syncs default to 6h: long syncs shift the whole schedule"
Key terms: default, fivetran, long, schedule, shift, syncs, whole
