Pyle

How to Troubleshoot a Failed ERP Sync ​

What This Task Does ​

This task helps you inspect a failed ERP sync request, identify the most likely cause, and decide whether it is safe to retry the request from the packaged ERP Bridge screen.

Use it when a record update, creation, or downstream sync does not appear to have reached the ERP as expected.

Before You Start ​

Make sure:

  • you have access to Settings > Erp Bridge
  • you know which record or sync flow failed
  • the ERP Bridge request log has already captured the request row you want to inspect

This guide is for the packaged request-log workflow only. It does not cover ERP connector setup, credentials, or host-app configuration screens that are not visible in the shared repo.

Steps ​

  1. Open Settings > Erp Bridge.
  2. Find the request log row for the failed sync.
  3. Inspect the first fields that usually explain the failure:
    • endpoint
    • HTTP method
    • response HTTP code
    • exception message
    • exception HTTP code
  4. Check whether the row includes enough context to replay the sync, such as a Retry sync action in the row menu.
  5. If Retry sync is available, use it only after you are confident the underlying data issue or transient ERP issue has been fixed.
  6. Re-open the log row after retrying and confirm whether the status or error details changed.
  7. If the row still fails, inspect the related business record next and verify the data that the ERP sync would have used.

What Happens Next ​

If the retry succeeds, the ERP sync flow may update the downstream business record outside the request log.

If the retry fails again, the request log remains the best place to confirm the endpoint, HTTP response, and exception details before you investigate the source record or the sync service path.

This task does not change business data by itself unless the retry completes successfully.

Common Mistakes ​

  • retrying a row before the underlying data problem is corrected
  • treating the request log as a connector-configuration screen
  • expecting every failed row to expose Retry sync
  • confusing ERP request logs with activity logs or comments on the record itself

Sources ​

  • packages/admin/routes/web.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/Page.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/DataTable.php
  • packages/admin/src/Livewire/Admin/Settings/ErpBridge/DataTable/Row/ActionsMenu.php
  • packages/admin/resources/views/components/settings/erp-bridge/data-table.blade.php
  • packages/erp-bridge/src/Models/RequestLog.php
  • packages/framework/src/Services/ErpBridge/AbstractErpSyncService.php