Review the logs before considering a manual retry.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Open the batch behind a synchronization status.
The business problem
Connector jobs were moving in the background without a clear operating picture. The dashboard was created as a front door into account health, fulfillment paths, and exception handling.
What we changed
Operators can move from the queue’s batch status into individual records, processing timestamps and exceptions.
What the team can do now
People can see the health of each account, identify what stopped moving, and recover without guessing whether the retry will duplicate work.
Follow an actual record
The batch label is only the start of the investigation.
The captured batch remains Partially Completed, although its counters show 22 records and 22 Done.
Records
22
Done lines
22
Batch state
Partially Completed
What the screen shows
The individual lines have processing timestamps and Done states. The remaining batch state needs investigation; the screenshot does not prove it was resolved.
What the team does next
Read the batch logs and confirm the remaining work before retrying or marking the batch complete.
What the next team receives
Support receives the batch reference, line outcomes and processing times needed to investigate.
How the work moves
Follow the work from one decision to the next.
01
Scope the account and fulfillment path
Products, merchant orders, fulfilled orders, sales, and schedules remain separated by account.
02
Process through explicit queues
Imports, exports, orders, shipments, tax, and tracking move through observable work units.
03
Expose the failure with context
The operator can see the account, record, action, and diagnostic information behind the stop.
04
Retry without creating a second problem
Idempotency, scoped jobs, and status checks make recovery safer and easier to explain.
Build notes and background
Data integrationOperational reporting
Make the exceptions part of the workflow.
Start with account scope
The seller and operation should be explicit before execution.
Check the filter before the empty state
A filtered result can be empty while the connector still has processing history.
Recovery needs source context
Inspect the account, queue and prior state before retrying; the capture does not demonstrate an actual recovery.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
Hardened and integrated existing commercial marketplace and shipping connectors with standard Odoo sales, product, stock, and delivery foundations. Toro’s work is the cross-connector operating layer, diagnostics, and recovery behavior described here.
