Scheduled Retry of Failed Uploads

When a Transaction Data Upload to the Central Platform fails — for example, due to a temporary network outage, an expired access token, or a non-2xx HTTP response — the staging record is set to status Error. The error is captured on the record (Reason Phrase, HTTP Status Code, Error Message).

Failed uploads can be retried in two ways:

  • Manually, by opening the Transaction Data Staging page, selecting the failed line, and choosing Retry Send Data. See Transaction Data Staging.
  • Automatically, by scheduling the Schedule Upload Mgt codeunit as a recurring job in the Job Queue.

Set up the scheduled retry job

  1. Click the icon, enter Job Queue Entries, and select the relevant link.
  2. Choose New to create a new Job Queue Entry and fill in the fields:
    FieldValue
    Object Type to RunCodeunit
    Object ID to Run10067299 (LSCAU Schedule Upload Mgt.)
    DescriptionRetry failed PLB transaction uploads
    Recurring JobEnabled
    Run on Mondays…SundaysEnable all days for continuous coverage
    Starting Time / Ending TimeCover the trading hours of the store
    No. of Minutes between RunsRecommended: 5 to 15 minutes
  3. Set the job to Ready to start the recurring schedule.

What the job does

Each time the job runs:

  1. It selects every Transaction Data Upload Header with status Error.
  2. For each record, it requests a new authentication token from the Central Platform using the credentials in PLB Setup.
  3. It re-sends the transaction JSON payload to the Central Platform API.
  4. On a successful response, the status changes to Submitted. On failure, the status remains Error and the error details are updated.

For the meaning of each upload status, see the status table in Transaction Data Staging.

Monitoring

  • Use Transaction Data Staging to view records by status and inspect the error details for any record that remains in Error after the scheduled retry.
  • Records that fail repeatedly may indicate a credentials issue (Authentication URL, Client ID/Secret, Resource) or a Central Platform service incident. Verify the connection via the Test connection button on the PLB Setup page.

See also

Transaction Data Staging

CDC Transaction Data to the Central Platform

PLB Setup