How do I manage and troubleshoot scheduled reports?
Use Scheduled reports to review schedules you own or receive, check past runs, and manage delivery settings for your own schedules.
A schedule is the recurring rule for a report. A run is one execution of that rule. A delivery is what the run sends to one email recipient or to a Secure File Transfer Protocol (SFTP) destination.
Open Reports & Analytics, then Scheduled reports. Search by schedule name or use the Status filter.
You can also open a report in Report Builder and select Scheduling in the sidebar to see its schedules, latest runs, and next runs.
As the schedule owner, open its row menu and choose an action:
Action | What it does |
|---|---|
Run now | Starts an extra run immediately. |
Run history | Opens past runs and their deliveries. |
Edit schedule | Lets you update the title, frequency, available report filters, and email recipients. |
Pause | Stops scheduled runs without removing the settings. |
Resume | Restarts a paused schedule. |
Remove schedule | Permanently archives the schedule and stops future runs. |
You cannot change the delivery method after creating a schedule. Create a new schedule if you need to switch between email and SFTP.
Pausing does not make up missed runs later. When you resume, the schedule continues at its regular frequency. Use Run now for an extra run if needed.
Removing a schedule is final. Archived schedules cannot be restored and are hidden unless you filter by Archived. Archiving or deleting the report also archives its schedules.
Avoid archiving the schedule's delivery workflow in Workflow Builder. Doing so stops the schedule.
Status | Meaning |
|---|---|
Active | The schedule runs when due. |
Paused | The schedule does not run until resumed. |
Ended | The schedule has reached its end date and has no remaining runs. |
Open Run history from the schedule's row menu. Review both the overall run and the individual deliveries. A successful delivery to one recipient does not mean every delivery succeeded.
Run status | Meaning |
|---|---|
Pending | The run is waiting to start. |
Running | Remote is generating and delivering the report. |
Skipped | The previous run was still in progress. Remote sent no files or emails for this run. |
Completed | The run finished without delivery failures. This includes no-data results. |
Completed with errors | Some deliveries succeeded and others failed. Remote emails the schedule owner. |
Failed | All deliveries failed, or the run could not start. |
Delivery statuses show what happened for an individual recipient or SFTP destination:
- Pending: the report is generating or waiting to upload.
- Delivered: Remote sent the email link or uploaded the SFTP file.
- No data: the email recipient's copy had no rows. Remote sent a no-data email instead of an empty file. This is not an error.
- Failed: generating or delivering the report failed.
For SFTP, a report with no rows still uploads a file containing only the column headers. It does not generate a no-data email.
The report has no data
Check the filters and reporting period used by the run. For payroll reports, confirm the relevant payroll is completed or finalized. For email delivery, also check the recipient's data access. Once the relevant payroll finishes, the schedule owner can use Run now.
Different recipients received different files
This is expected when their data access differs. Remote generates each email recipient's copy using their permissions at run time. Recipients cannot open one another's copies.
A new role member did not receive the report
Remote saves role members as recipients when you save the schedule. Later role or sharing changes do not update it automatically. Review and resave the schedule's recipients.
Only one recipient's delivery failed
Check whether that recipient still has access to the report. Losing access affects their delivery, not the other recipients' deliveries. Inactive recipients are skipped.
A monthly run did not happen
Check the selected day. Dates 29 to 31 are skipped in shorter months. Also check whether the schedule is paused, ended, or archived, and whether a previous run was still in progress.
An SFTP failure email arrived hours later
Remote retries uploads over about 8.5 hours before emailing the owner after the final failed attempt. Check the server connection, credentials, folder access, and allowed Remote IP addresses.
When a schedule owner is deactivated, offboarded, or removed as an admin, active and paused schedules normally move to the company owner. Ended and archived schedules do not move.
- Active email schedules continue running and keep their recipients. If the previous owner was the only active recipient, Remote adds the company owner as a recipient.
- SFTP schedules are paused because the exported file would now use the company owner's access. The company owner should review the report and destination before resuming delivery.
- The company owner receives view access to the report if needed, plus an in-app notification and an email about the transferred schedules.
A schedule may stay with the previous owner and be paused if it uses a draft report or the company owner cannot take it. This can happen when there is no active company owner, Scheduled reports is not enabled for them, their role cannot read the report's data, or the report author has removed them from the report.
If a run detects that its owner can no longer read data exports or the report's data, that schedule also moves to the company owner where possible. Remote removes the previous owner from its recipients. Transferred SFTP delivery is paused for review.
The company owner can turn off transfer emails under Report schedules moved to you in notification settings. In-app notifications still appear. Remote still sends the email if a transferred SFTP schedule remains paused.
