Skip to content
SupaCloud Docs
Select themeSelect language

Schedule a report

A scheduled report delivers a workspace’s report on a recurring cadence to the channels you choose, so you do not have to open Reports to keep an eye on agent work. The report is rendered from the same figures you see in the UI and sent on your schedule.

The Reports Overview also surfaces delivery figures — a funnel of how far work got, merged pull requests, and how many project and user documentation files the standard closeout updated — alongside the cost and usage figures. See the Reports reference for what each tab carries.

Where to configure them

Section titled “Where to configure them”

Scheduled reports live in the Reports hub under Reports → Scheduled reports — the single place to create and manage them.

The Scheduled reports tab listing each schedule with its cadence, send times and recipients.The Scheduled reports tab listing each schedule with its cadence, send times and recipients.

Scheduled reports are workspace-scoped. Switch workspaces first if you want to schedule reports for a different workspace.

Create a scheduled report

Section titled “Create a scheduled report”

  1. Open Reports → Scheduled reports and start a new report.

  2. Pick the cadence:

    Cadence When it runs
    Daily Every day
    Weekly Once a week
    Monthly Once a month

  3. Set one or more send-times. A schedule can have more than one send-time per day — for example a morning and an end-of-day delivery — so add each wall-clock time you want the report sent.

  4. Choose the delivery channels. A report can go to one or more of:

    • Email
    • Discord — to your linked Discord
    • Telegram — to your linked Telegram

    Discord and Telegram delivery use the chat account linked to your workspace; link a bot first if you have not (see the related how-to pages below).

  5. Set the scope — what the report covers for this workspace.

  6. Save the schedule. It is queued for its next due send-time; the report is not sent immediately.

Manage scheduled reports

Section titled “Manage scheduled reports”

Both surfaces list the workspace’s scheduled reports with their cadence, send-times, and channels. From the list a workspace admin can edit a schedule’s cadence, send-times, channels, and scope, or remove a schedule when it is no longer needed.

Check whether a report was actually delivered

Section titled “Check whether a report was actually delivered”

The scheduled-reports list carries two counters over every delivery attempt the workspace has made: Sent and Failed.

A delivery counts as Sent only when the transport accepted it — the SMTP relay returned success, or the chat platform accepted the message. An email that could not be handed to a relay at all (no SMTP configured on this instance, an unreachable or misconfigured host, a rejected recipient, an expired relay password) counts as Failed, never as sent.

When the failed counter is above zero, the most recent failures are listed underneath it — each naming the schedule, the channel, when it happened, and the reason the transport gave. That reason is what tells you whether to fix the SMTP configuration, re-link a chat account, or correct a recipient address.

A channel that had nothing to attempt is not counted at all: an enabled email channel with no recipient address to resolve, or an enabled chat channel with no linked account, is skipped silently rather than logged as a failure.

If the recipient of a schedule leaves the workspace, the schedule stops delivering — workspace data is never pushed to someone who no longer has access. The workspace owner is notified when that happens, so the schedule can be re-pointed at an active member or disabled.

See also

Section titled “See also”