Overview

Scheduler is the surface where users create and manage scheduled jobs, recurring or one-time runs that deliver Lens Reports to recipients. A scheduled job consists of a schedule definition (timing, frequency, recurrence) and one or more tasks that describe what to run and where the output goes.

Scheduler is reached from the Scheduler option on the Main Navigation Bar. The page has two tabs: Jobs lists scheduled jobs with their status and per-row actions; Audit lists individual job and task runs with status and error detail.

When to use it

• A Lens Report needs to be delivered to recipients on a recurring schedule (daily, weekly, monthly).
• A Lens Report needs to be delivered once at a specific time (Adhoc).
• A single schedule needs to deliver multiple Reports in the same run — model these as multiple tasks under one job.
• A Report needs to be sent to a connector destination (SFTP, Azure Blob, S3, and similar) rather than to a user.

Page tabs

Creation paths

Three entry points all create a scheduled job. The job structure they produce is the same; only the entry UX differs.

Job fields

Task fields

A task defines what the job actually delivers when it runs. A job carries one or more tasks; all tasks under a job run on the same schedule.

Delivery options

Jobs tab columns

Audit tab

The Audit tab logs run-level history with one row per job execution. Used for monitoring delivery health and diagnosing failures.

Failed runs surface an error code on hover. The codes identify the stage at which the run failed and are useful for routing the issue to the right area:

Key behaviors

One job, one or more tasks. A job carries a single schedule definition and any number of tasks under it. Multi-task jobs deliver everything on the same recurrence — useful for stakeholder packs that combine several Reports triggers in one delivery cycle.

Three creation paths, same outcome. Whether a job is created from the Scheduler page, the HTML button on a Report, or the Filter Panel on a Dashboard, the resulting object is the same job structure managed in the Jobs tab. The shortcuts trade off some configuration depth for faster creation in context.

Filter overrides are per-task. A task can override the source Report’s default filters via the Filter Configuration dialog. The override applies only to that task’s delivery and does not modify the Report’s design-time filter configuration. Filters appear in the task UI only when the Report has filters defined.

Password protection is per-task. If a task carries a password, the delivered file requires the password to open. The password is stored with the task and applied to every run; recipients receive the password through a separate channel chosen by the job creator.

Audit is run-level, not job-level. The Audit tab logs each run separately, so a daily job that has run 30 times produces 30 audit entries. This makes it possible to diagnose intermittent failures and track delivery health over time.

Failed runs do not block subsequent runs. A failed run records an error in the Audit tab but does not prevent the next scheduled run from executing. Persistent failures should be diagnosed using the error codes and corrected at the source (Report, Workflow, or destination) rather than retried at the Scheduler level.