Scheduling reports in Business Central: the Report Inbox and the job queue underneath

Reporting · 7 min read

Every store runs the same reports on the same rhythm: sales at close, inventory on a cycle, the same figures for the same meeting. Running them by hand, from the request page, every time, is pure waste — and running a heavy report while cashiers are working slows the system for everyone. Business Central can schedule those reports once and deliver them on their own. The catch is that the feature is really three features wearing one coat, and a missing report can be lost in any of the three. Here is the whole path, end to end.

How the three pieces fit together

The Schedule option is the front door. On the report's request page, after choosing Send to, the Schedule option captures the options and filters currently on the request page — those exact options are what get applied when the scheduled job later executes.

The job queue is the engine room. Scheduling creates a job queue entry, and the report runs when the job queue processes that entry at the scheduled time, the same as any other scheduled task. Everything about the run after that first moment — timing, recurrence, output, errors — lives on the job queue entry, not on the report.

The Report Inbox is the delivery shelf. When the scheduled output is a file, the finished report is placed in the Report Inbox on the Role Centre for the user who scheduled it. Nothing is emailed, and nothing is downloaded automatically. Most "the report never arrived" stories are really "the report arrived somewhere the user never looked."

Set up a recurring retail report, step by step

1. Open the report and set it up exactly as it should run. Choose the filters and options on the request page first — a daily sales report filtered to the right posting dates and locations, an inventory report filtered to the store. The scheduled run reuses these options verbatim.
2. Choose Send to, then Schedule. The Schedule option sits behind the Send to button on the request page.
3. Pick the output type. Save to a file (PDF, Word, or Excel), print it, or only generate it. File output is what lands in the Report Inbox; printed output goes to the printer selected here.
4. Set the earliest start date and time — for a sales report, after close of business, when the day's posting is done and the system is quiet.
5. Set the recurrence with the Next Run Date Formula. The formula calculates the next start date and time after each run. Microsoft's documented example: D4 runs the report every Thursday — a natural fit for a weekly inventory report. A daily report uses the equivalent day-by-day formula.
6. Add an expiration date and time if the schedule is temporary — a seasonal report, for example, should stop on its own rather than run forever.
7. Confirm the entry, then check its status. Scheduling creates the job queue entry. On the Job Queue Entries page, a newly created entry starts with status On Hold; use Set Status to Ready so the entry is actually armed to run.

What success looks like: after the first scheduled run, the report file is sitting in the Report Inbox in the format chosen, and — for a recurring schedule — the entry is still listed on Job Queue Entries with its Earliest Start Time advanced to the next run. A one-time schedule behaves differently by design: once it has been processed, the item is removed from the job queue.

Where the output lands: the Report Inbox

The Report Inbox page lists the scheduled reports generated by the user, and the same list is available as a part on the Role Centre. A few behaviours are worth knowing before they surprise anyone:

• Only scheduled output appears. Reports produced with the Print action, or saved as a file from the Reports menu, are not listed in the Report Inbox. It is a shelf for scheduled runs, not a history of every report.
• The format was fixed at scheduling time. The file is saved in the format defined when the report was scheduled. To change the format — or the recurrence — edit it on the Job Queue Entries page, where those settings live.
• Open in OneDrive copies the report to the Business Central folder in OneDrive and opens it in a new browser window, ready to print or manage as a document.
• Share sends a link, not an inbox copy. The Share action makes the file available to other users on OneDrive for Business; the report does not appear in their Report Inbox. A colleague who "doesn't have the report" may have a link instead.
• Expiring reports linger in OneDrive. A report set to expire on the Schedule a Report page and copied to OneDrive is not automatically removed from the shared folder — clean those up manually.
• Delete old output from the inbox — singly, or several at once with Select more — so the shelf stays a current shelf, not an archive nobody trusts.

And the expectation to kill early: scheduling alone does not email a report. The Schedule action creates a job queue entry and puts file output in the Report Inbox — full stop. Per the Dynamics Community answers on exactly this question, emailing a scheduled report takes customisation or Power Automate. Set that expectation when the schedule is created, not when the inbox stays empty.

When a scheduled report does not arrive: the diagnosis sequence

Work the layers in order. Each check eliminates one piece of the machine:

1. Is the output type a file? Printed output went to the selected printer, and "generate only" produces no file at all. Only file output lands in the Report Inbox.
2. Does the job queue entry still exist? Open Job Queue Entries. A one-time entry that already ran is gone — that is success, not loss. For a recurring entry, check the Earliest Start Time: if it has advanced past the missing run, the entry believes it ran.
3. What is the entry's status? On Hold means it was never armed — Set Status to Ready. Error means it ran and failed — use Show Error to read the message. The full status vocabulary is Ready, In Process, On Hold, On Hold Due to Inactivity, Waiting, Error, and Finished.
4. What do the log entries say? Job queue data is stored for troubleshooting: select the entry and choose Log Entries to see its run history, including failures, instead of guessing.
5. Is it a transient failure? Entries stop running when an error occurs. Instead of babysitting retries, set Maximum No. of Attempts and Rerun Delay (sec.) so a failing entry retries on its own — the combination can keep an entry trying until an external service comes back. To retry manually, restart the entry: set it On Hold, then Ready, or use restart.
6. Was the environment copied? On the Scheduled Tasks page, tasks belong to a company in a specific environment — and all scheduled tasks stop if the company sits in an environment that is a copy of another environment. After an environment refresh, silent schedules are the default, not a mystery.
7. Is anyone looking in email? See above: nothing was ever going to arrive there.

For the estate-wide view of failed overnight jobs, telemetry carries the same story — see what to monitor in a retail estate.

Keeping the schedule healthy

• Do not over-schedule. Microsoft warns that recurring job queues can affect performance and should not run too frequently — pick the largest interval that still serves the business. A sales report needs to be daily; it does not need to be hourly.
• Watch the cue, not the inbox. The Job Queue Tasks cue on the home page shows tiles for Tasks Failed, Tasks in Process, and Tasks in Queue; a task lands in Tasks Failed after it exceeds the entry's maximum attempts. That tile is the morning check.
• Use My Job Queue for personal schedules. The My Job Queue part shows entries the user started that are not finished, and whether an error occurred — and it can be added to the home page if it is not displayed.
• Turn on failure notifications. The Set Up Job Queue Notifications assisted setup chooses who gets told about a failure — the person who started the entry, job queue administrators, or both — and how, including in-product notifications or a Power Automate flow subscribed to the Job queue task failed business event.
• Edit schedules on the entry, not the report. Once a report is scheduled, changes happen on the job queue entry: the report options through the Report Request Page action, and the output in the Report Parameters FastTab.

FAQ

Can a scheduled report be emailed automatically?
Not by the Schedule flow itself. It creates a job queue entry and delivers file output to the Report Inbox. Email delivery requires customisation or Power Automate.

Why did a scheduled report disappear from the job queue?
If it was scheduled to run once, removal after processing is the designed behaviour. Recurring entries stay, with the Earliest Start Time moved to the next run.

How is the file format of a scheduled report changed?
On the Job Queue Entries page, where the format, recurrence, and other settings for the scheduled report are maintained.