Understand marketplace sync jobs

Marketplace imports and write-backs run through a shared job framework with history, retries and duplicate prevention.

2 min read · Updated 16 July 2026

Problem

External APIs can be temporarily unavailable, rate-limited or missing credentials, so a single request cannot be assumed to succeed.

Solution

Review each sync attempt, allow eligible retries to use backoff and use diagnostics when a failure persists.

Job lifecycle

A sync job moves through pending, running, completed, retrying or failed states. Each execution creates immutable run history.

Duplicate prevention

Logivio avoids creating another active job for the same connection and operation.

Retry behaviour

Temporary failures use exponential backoff. Persistent failures remain visible in Sync diagnostics and Seller Health.

Credential-safe operation

When provider credentials or access tokens are unavailable, jobs fail safely without changing marketplace data.

Frequently asked questions

Will Logivio retry a failed marketplace sync?

Eligible temporary failures are scheduled again using exponential backoff.

Can two identical active sync jobs run at once?

No. Active duplicate jobs are prevented for the same connection and operation.

Based on this article and adjusted to avoid guides already viewed in this session.

Was this article helpful?

Report a problem with this article

Use this for incorrect, outdated, confusing, or broken content.