## TL;DR

Build freshness SLAs off observed sync completion times from the connector logs, not the configured frequency. Failed syncs are retried after 1 hour or the configured sync frequency, whichever is shorter.

## Steps

1. 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.

## When to use

You are seeing this: 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. Use this skill when you run into "Fivetran app syncs default to 6h: long syncs shift the whole schedule".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.