Scheduled tab

The Scheduled tab of the Reports screen sends a saved report to a list of recipients on a repeating timetable. It’s how stakeholders get the numbers without signing in to Testver.

The schedule table

Each row is one recurring dispatch job:

Column	What it shows
Title	The schedule’s name.
Source	The saved report being sent (“Missing” in red if it was deleted).
Schedule	The timing in words — “Mondays at 09:00”, “Monthly on day 1 at 08:00” — and, below it, the next run (while the schedule is enabled). Hover it for the cron expression.
Format	PDF, XLSX, DOCX or HTML — the file recipients receive.
Recipients	Who it goes to (the count when there are several; hover for the list).
Last run	When it last dispatched.
Status	Success; Sent · stale data (amber) when the email went out but the data refresh failed, so it carried the last saved values — hover for why; Error when nothing was sent — hover for the message; paused; — when it hasn’t run yet.
Actions	Run now (Play icon), PAUSE / RESUME, EDIT (opens the Edit schedule dialog — the source report can’t be changed there; Save changes keeps the edit), and Delete.

A Refresh button re-reads the list (it also refreshes on its own every 20 seconds), and New schedule opens the dialog. Creating, changing and running schedules need the Tester role or higher.

Creating a schedule

1. Open the Scheduled tab and click New schedule.
2. Give it a Title (for example “Weekly QA Summary”).
3. Pick the source report — it must already be saved in My Reports.
4. Set the timing with the cron builder — the same one used by Advanced → Schedules and suite schedules. Its tabs are Minutes, Hourly, Daily, Weekly, Monthly and Advanced (each cron field set by hand); it shows the timing in words, the cron expression and the next three runs.
5. Choose the format: PDF (the default), Excel, Word or HTML.
6. Enter the recipients, comma-separated (up to 25).
7. Leave Enabled on (click it to create the schedule Paused), then click Create schedule. The job appears in the table and fires on its own from then on.

The Weekly tab of the cron builder picks the days and the time, and previews the next runs:

You can also ask for it in the AI Assistant: in Reporting mode, “email this dashboard to qa-leads@example.com every Monday at 9” saves the dashboard if needed and creates the schedule — after you approve it (creating or changing a schedule always asks, even in the chat’s Auto mode).

What each run does

1. Refreshes the report with current data (the same read-only refresh as Regenerate with current data) and saves it — so the saved report, and its share link if it has one, then show the values that were just sent.
2. Builds the attachment in the chosen format from that refreshed dashboard — the same file the report’s Download menu gives you.
3. Emails it, with the headline KPIs in the email body. The attachment is deleted from the server once sent.

If the refresh fails, the email still goes out with the last saved values, says so in the email, and the row shows Sent · stale data. If the run fails altogether, the row shows Error and the schedule’s owner gets one email saying so — sent through the same email connector, to the address on their Testver account — and not another until the schedule has worked again.

Tip

PDF opens anywhere and gets past mail gateways that strip HTML attachments. Choose Excel when recipients want to sort and filter the numbers.

Tip

Use Run now the first time you create a schedule. It confirms the recipients and the rendered output are right, without waiting for the next cron slot. Run now is refused while that schedule is already sending and for a minute after it ran, so a double click never sends the email twice.

Related

• Reports overview — the screen and its four tabs.
• My Reports tab — where the source report must be saved first.
• Advanced → Schedules — scheduling a test run rather than a report.
• Connectors — the email configuration that delivery depends on.