The Runs & Jobs tab of the Integrations Dashboard lists every POS import run across the locations the user can access. Each row shows the business date, how the run started, how far it got, and the outcome. Selecting a run opens the run details, which show each attempt and the stage where a failed run stopped.
Learn more about the Dashboard in the Integrations Dashboard Overview.
From this page, users can:
Search and filter runs, for example to list only failed runs.
Open a run to see its stages and attempts.
Copy the error code of a failed run to share with R365 Support. See Troubleshoot a Failed POS Import with the Dashboard.
Track a re-sync after it starts. See Re-sync POS Data from the Dashboard.
Security
Users must have a User Role and one of the following permissions to view the Runs & Jobs tab:
Administration → Integrations →
3rd Party POS View Only
3rd Party POS Sync
3rd Party POS Admin
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.
Navigation
Navigation Menu
Select Admin from the left navigation rail.
Under Integrations, select Dashboard.
Select the Runs & Jobs tab.
Search
Navigate to pages with the R365 global search bar:
Enter all or part of the page name in the R365 global search bar.
Select the page from the results list.
Only enabled pages can be searched for. If the desired page is not enabled, contact your CSM for assistance.
Page Buttons and Fields
Runs & Jobs Tab
Button/Field | Description | |
|---|---|---|
1 | Search | Narrows the list to runs that match the text entered. |
2 | Filters | Opens column filters. Filters stay in the page address, so a link to the page opens the same filtered list. |
3 | Columns | Chooses which columns the list shows. The Location column cannot be hidden. |
4 | Refresh | Reloads the list. |
Columns in the runs list:
Column | Description |
|---|---|
Location | The location name. |
Business date | The date of the sales the run imported, for example Mon, Oct 19, 2026. |
Trigger | How the run started. Scheduled is the nightly import. Manual is a re-sync that a user started from the Dashboard. |
Triggered by | The name of the user who started a Manual run, or ‘Scheduled job’ for a nightly run. Shows a dash when the source is not known. |
Furthest stage | The last pipeline stage the run reached, shown with its position, for example ‘Batch requested 3/5.’ |
Outcome | The result of the run. See the Run outcomes table below. Hovering shows the stage and the error message for a failed run. |
Error category | The broad group the failure belongs to. See the Error categories table below. |
Attempts | The number of times the import ran for that location and business date. A Manual run always shows 1. |
Started | The date and time the run started. The list sorts by this column, newest first. |
Duration | How long the run took, or ‘In progress’ while it runs. |
Run Details
Click a row in the Runs & Jobs table to open the Run Details.
Button/Field | Description | |
|---|---|---|
1 | Header and details | The location, business date, and outcome, followed by the trigger, duration, number of attempts, and start time. The open run stays in the page address. |
2 | Failure alert | For a failed run that reports an error, an alert reads "Failed at" followed by the stage, with the error message below it. A run that reports no error shows no alert. The title and message come from the error code. See the Import error messages table below. |
3 | Copy error code | Copies the error code of the run so it can be shared with R365 Support. |
4 | Pipeline overview | A bar that summarizes the progress of the run. |
5 | Attempts | One row for each attempt, with the most recent attempt expanded. Each row shows the stages Processing, Extracted, Batch requested, Transforming, and Transformed, each marked Completed, Failed, In progress, or Not started. Earlier attempts show as Failed. The timeline is an estimate. On a re-sync run, only the furthest stage shows elapsed time. |
A failed run with no reported error shows no alert. Contact R365 Support and include the business date and the location.
Pipeline Stages
Every run moves through the same stages. The Furthest stage column and the run details show where a run stopped.
Stage | What it means |
|---|---|
Processing | R365 picked up and started the import. |
Extracted | R365 pulled the sales data from the POS. |
Batch requested | R365 was asked to build the Daily Sales Summary. |
Transforming | R365 is building the Daily Sales Summary. |
Transformed | R365 created or updated the Daily Sales Summary, and the run is done. |
Zero-Activity | A business date that imported with no sales. The run moves through Processing and Extracted, shows as 3 of 3 steps, and counts as a success. The day shows as zero dollars. |
Run Outcomes
Outcome | What it means |
|---|---|
Completed | The run finished, and R365 created or updated the Daily Sales Summary. |
Failed | The import stopped and will not finish without help. A run fails when the data could not be pulled from the POS, when the Daily Sales Summary could not be built, or when the Daily Sales Summary for that date was already approved. When any part of a run fails, the whole run shows as Failed. The needs attention banner counts failed runs. |
In Progress | The run has started and has not finished. |
Queued | The run is waiting to start. |
Pending | [PLACEHOLDER: definition of Pending] |
Zero Activity | The business date imported with zero sales. The Dashboard shows the day as zero dollars and does not explain why. |
Error Categories
The Error category column groups a failed run by cause. The specific message for each run comes from the error code.
Category | What it means | Who acts |
|---|---|---|
Auth | The POS rejected the saved credentials, so nothing imported. | Reconnect the POS. R365 does not retry this failure automatically. |
Validation | Required setup or data is missing or wrong for the location. A business date with no sales activity also shows as Validation. | Fix the location or POS setup. A date with no sales activity needs no action. |
Dependency | The POS or another service was unavailable or timed out, or a file was not there yet. | No action. R365 retries automatically. When the failure keeps happening, the POS may have a problem. Contact R365 Support. |
Rate limit | The POS is limiting how many requests R365 can make. | No action. R365 retries later. |
Internal | Something in R365 stopped the import. | Contact R365 Support. |
Contract | The POS sent data in an unexpected format, usually after a POS update or export change. | Fix the issue at the POS, or contact R365 Support. |
Unknown | R365 could not identify the cause. | Contact R365 Support and include the link to the run. |
Import Error Messages
The failure alert in the run details shows a title and message that match the error code of the run.
Title | Message |
|---|---|
Daily Sales Summary not created yet | Sales for this business date arrived, but the Daily Sales Summary wasn't created. |
POS credentials not accepted | The POS didn't accept the saved credentials, so sales for this business date weren't imported. |
Location setup incomplete | A required POS setting for this location is missing or incorrect. |
Location or POS setup needs attention | A location or POS setting for this import is missing or incorrect. |
POS couldn't be reached | The import couldn't connect to the POS or didn't get a response in time. |
POS temporarily unavailable | The POS reported that it's temporarily unavailable. |
POS request limit reached | The POS limited the number of requests, so the import stopped. |
Import could not be started | An issue in R365 stopped this import before it could start. |
Sales import could not be completed | An issue in R365 stopped this import. |
POS sales file not available yet | The POS export for this business date wasn't available when the import ran. |
Labor setup incomplete | Required labor settings for this location are missing. |
POS sent unreadable data | The POS returned data in a format that can't be read. |
Import could not be completed | The import stopped for a reason that has not been identified yet. |