Scheduled Reports
Deliver reports automatically on a recurring schedule.
#Purpose
Get reports to stakeholders without manual effort.
#Business goal
Consistent visibility for the people who need it.
#At a glance
| Detail | Value |
|---|---|
| Estimated time | Setup, then automatic |
| Departments involved | Leadership, Operations |
| Business modules used | Reports, Automation |
| AI departments used | — |
| Required permissions | Reporting access; admin/CEO to trigger a run |
| Prerequisites | A report schedule with recipients. |
#Workflow at a glance
1
Set schedule
Report & recipients.
2
Job runs
On cadence.
3
Report delivered
To recipients.
4
Confirm
First delivery.
#Step by step
1
Set up a schedule
Choose the report, cadence, and recipients.
2
The scheduled-reports job runs
It delivers on the cadence you set; an admin or CEO can also run it manually.
3
Recipients receive it
The report arrives automatically.
4
Confirm delivery
Check the first scheduled report was received.
#Approval points
No formal approval gate
This workflow does not require a sign-off step, but you can still review before acting.
#Expected result
What you should see
Reports are delivered automatically to the right people on schedule.
#Common mistakes
- Wrong recipients.
- Not confirming the first delivery.
#Troubleshooting
| If this happens | Try this |
|---|---|
| A scheduled report did not arrive | Confirm recipients and that email delivery works. |
| Run it now | An admin or CEO can trigger the scheduled-reports job manually. |
#FAQ
Can I run a scheduled job on demand?
Yes — admins/CEO can trigger it manually via run-now.
#Keep exploring
#Related workflows
#Knowledge base
#Business modules
Reports Module
Reports.
Automation Module
Jobs.
Getting Started
Set up your workspace.
Platform Overview
How the OS fits together.
Still need help?
Can’t find what you’re looking for? The DevSphere OS team is happy to help.
Was this page helpful?