The Sync Log (3PL Connector > Sync Log) is the connector's flight recorder: one entry per operation - scheduled or manual, in or out, success or failure - with the complete request and response (headers included, credentials always redacted), and a full account of every action the connector took in Odoo as a result. When something looks wrong anywhere in the app, the answer is in here.

Anatomy of a log entry

The log opens as a card feed: each card is colour-coded by outcome (green done, orange warnings, red active error, blue queued, grey acknowledged/skipped) and shows the flow, entry reference, instance, the business record it concerns, when it ran and how long it took, the error text where there is one, and Retry / Acknowledge / Record buttons right on the card. A Refresh button sits at the top of the view - use it while waiting for a just-triggered or queued job to finish. A classic list view is one click away for filtering-heavy work, and both share the same filters (Active Errors, Warnings, Queued, Today, group by instance/flow/status/date).

Opening an entry shows four tabs:

• Actions in Odoo - the step-by-step record of what the connector actually did in your database for this operation: validated transfer X (with the exact quantities and lots written), created lot/batch Y, set carrier and tracking on Z, created backorder, created return receipt, routed damaged units, created draft credit note, marked the order sent/despatched… Each action links to its record.
• Records - the de-duplicated list of every Odoo document this operation touched, each a click away.
• Request and Response - the complete HTTP exchange with the 3PL in a code viewer: method, full URL, query parameters, headers (credentials always redacted) and body on the request side; status code, response headers and body on the response side. An operation that made several calls - a paginated product list, a token refresh before the real request - shows every exchange in order.

Outcomes:

• Queued - background work accepted but not yet executed (e.g. a bulk product push). The entry flips to Done when the queue drains; each processed item logs its own entry as it completes.
• Done - succeeded.
• Done with Warnings - succeeded, but something a person should know about happened (e.g. an un-batched despatch shipped from the UNBATCHED pool). Counted on the dashboard's Warnings card.
• Error - failed; counted as an active error until resolved.
• Skipped - deliberately not performed (e.g. an empty batch).