A POS import can fail for a location on any business date. The Integrations Dashboard shows which locations have a failed import, the stage where each import stopped, and a message about the cause. This article walks through finding a failed import on the Runs & Jobs tab and reading its details.
When an import fails, the system does not create or update the Daily Sales Summary for that business date. Learn more about other causes for missing and out of balance daily sales summaries.
Security
Users must have a User Role and one of the following permissions to view failed imports:
Administration → Integrations →
3rd Party POS View Only
3rd Party POS Sync
3rd Party POS Admin
Re-syncing after a fix requires the 3rd Party POS Sync or 3rd Party POS Admin permission. See Re-sync POS Data from the Dashboard.
These permissions can be added to custom user roles or individual users. The Permission Access report can be used to determine which user roles or users already have these permissions assigned. For more information, see User Setup and Security.
Find Why an Import Failed
Follow these steps to find a failed import and read its cause:
Click steps to expand for additional information and images.
1) Navigate to the Integrations Dashboard.
Select Admin from the left navigation rail.
Under Integrations, select Dashboard.
2) Select View runs on the ‘needs attention’ banner.
The banner counts locations whose latest import failed. A location leaves the banner when a later import for that location does not fail, or when the failure is older than 7 days.
To look for a failed import without the banner, open the Runs & Jobs tab and filter the Outcome column to Failed.
3) Narrow the list to the location and business date. (Optional)
The Runs & Jobs tab opens with the list filtered to failed runs in the banner window. The filter replaces any filters already set on the tab.
Use Search and the column filters, for example the Location, Business date, or Error category filters.
4) Select the run to open its details.
The run details panel opens on the right side of the page.
5) Read the failure alert.
For a failed run that reports an error, the alert reads "Failed at" followed by the stage where the import stopped, with a message about the cause. See Integrations Dashboard: Runs & Jobs Tab and Run Details for the list of messages.
A failed run with no reported error shows no alert. Contact R365 Support and include the business date and the location.
6) Check the Error category to see who acts.
The Error category column groups the failure by cause. Some categories need action from the customer, such as reconnecting the POS or fixing the location setup. Others retry automatically or need R365 Support. See the Error Categories table in Integrations Dashboard: Runs & Jobs Tab and Run Details.
7) Expand an attempt to see the stages.
Each attempt shows the stages Processing, Extracted, Batch requested, Transforming, and Transformed. A run that retries shows one row for each attempt, and earlier attempts show as Failed. The timeline is an estimate.
8) Select Copy error code to share the cause with R365 Support.
The button copies the error code for the run. The code does not appear on screen, so paste it into the support request along with the business date and the location. Contact R365 Support.
Re-sync After the Cause Is Fixed
After the cause is resolved, re-sync the business dates that failed. Re-syncing requires the 3rd Party POS Sync or 3rd Party POS Admin permission. See Re-sync POS Data from the Dashboard.
If the re-sync fails again, copy the error code from the new run and contact R365 Support with the business date and the location.