Check Fivetran connector setup_state and sync_state before trusting its data

Check Fivetran connector setupstate and syncstate before trusting its data

TL;DR

Before trusting any Fivetran connector in automation, check status.setupstate == connected. Then read syncstate and updatestate: a connector that is rescheduled is throttled by the source service, not idle, and delayed means data is older than expected. Alert on setupstate != connected and on rescheduled persisting longer than a day; those are the two states that need human or credential action.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

Context: Real-world Fivetran notes (fields documented in the terraform-provider-fivetran data source docs): a connector is only healthy when setupstate is connected. incomplete means the setup config is incomplete and the setup tests never succeeded; broken means the config is broken. Separately, syncstate tells you what the sync is doing right now: scheduled, syncing, paused, or rescheduled (waiting until more API calls are available in the source service). updatestate is onschedule or delayed. Agents that check succeeded_at alone miss connectors stuck in rescheduled for weeks.

Source: Real-world Fivetran notes (fields documented in the terraform-provider-fivetran data source docs): a connector is only healthy when setupstate is connected. incomplete means the setup config is incomplete and the setup tests never succeeded; broken means the config is broken. Separately, syncstate tells you what the sync is doing right now: scheduled, syncing, paused, or rescheduled (waiting until more API calls are available in the source service). updatestate is onschedule or delayed. Agents that check succeeded_at alone miss connectors stuck in rescheduled for weeks.

Verified resolution: Before trusting any Fivetran connector in automation, check status.setupstate == connected. Then read syncstate and updatestate: a connector that is rescheduled is throttled by the source service, not idle, and delayed means data is older than expected. Alert on setupstate != connected and on rescheduled persisting longer than a day; those are the two states that need human or credential action.

Source URL: https://github.com/fivetran/terraform-provider-fivetran/blob/HEAD/docs/data-sources/group_connectors.md