Import and refresh lifecycle

Reliable execution

A job has stable identity, account scope, and period. A worker holds a bounded lease and heartbeat, then completes once. Retry must not duplicate facts.

Failures

• Transient failures receive bounded backoff.
• Authorization failures require connection repair.
• Schema failures retain evidence and block unsafe parsing.
• Exhausted retries move to an investigation queue.

First marketplace import

Start sync queues an initial import for every active marketplace connection with stored credentials. The request being accepted does not mean that data is already available. Review import jobs and dataset freshness.

The onboarding step completes only after successful import jobs and a successful refresh from raw data to analytics. A dry run or failed job does not complete the step. Resolve credential or permission errors, then retry; an active job is reused rather than duplicated.