Working an error - retry, acknowledge, support tickets

Working an error - retry, acknowledge, support tickets

The three ways to act on a failed entry, plus the support tooling behind them - all built so nothing personal ever leaves your database.

Working an error

Retry. Re-executes the exact operation the entry refers to. A successful retry links back to the original and automatically acknowledges it, so the error count self-heals.

Acknowledge. For errors that need no (further) action - a one-off timeout that a later scheduled run already covered, a test order the 3PL rejected on purpose. Acknowledging keeps the entry for history but removes it from the active-error count (dashboard Errors card). Acknowledged-by and when are recorded; Re-open Error (Admin) undoes it. Acknowledge instead of deleting - the log is your evidence.

Email Support. On any error or warning entry, opens a pre-filled email to the provider's support contacts (configure them on the provider card: one primary To, comma-separated secondary CCs) in your desktop mail client. Everything that leaves Odoo is PII-redacted: customer names, addresses, emails and phone numbers are masked in both payloads and free text - over-redaction by design. Clicking the button also downloads two files - sync-<entry>-request-redacted.json and sync-<entry>-response-redacted.json - ready to attach to the email, and stores a full redacted text report on the log entry itself.

Raise Support Ticket. The one-click alternative: sends the same PII-redacted report, with both redacted payload files attached, straight to your help desk's ticket intake address - the desk turns it into a ticket automatically, no mail client involved. Configure the intake address under Settings > 3PL Connector > Raise Support Tickets by Email (requires an outgoing mail server on the database). Every raised ticket is noted in the instance's chatter with who raised it.

In-app help widget. With a Zoho Desk ASAP add-on configured (Settings > 3PL Connector > In-App Help Widget), connector users get a floating help launcher inside Odoo: Knowledge Base search over this documentation, the Zia Answer Bot, and ticket submission - without leaving the screen they are stuck on.

    • Related Articles

    • Roles and permissions

      Access to the connector is controlled by a single role picker on each user (Settings > Users > 3PL Connector): Read Only, Ops or Admin. Each level includes everything below it, and every button in the app is role-aware - users simply do not see ...
    • Common errors and FAQ

      Common errors and what they mean Error text contains Meaning Fix "no Sprint warehouse mapping" order's Odoo warehouse is not mapped on the instance add the warehouse mapping, retry "has no Internal Reference (SKU)" product cannot be identified to the ...
    • The Sync Log explained

      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 ...
    • Reading the dashboard

      The app opens on the Dashboard: one card per instance with live metrics, day-on-day variances and every routine action one click away. This page explains each number, the variance arrows, the inactive states, and the Perform Operation popup used ...
    • Install the app and assign roles

      Step 1 - Install Install LataSys: 3PL Connector from the Apps menu. The module depends on Sales, Inventory (with delivery), Purchase and Expiration Dates - Odoo installs these automatically if they are missing. After installation a new 3PL Connector ...