Scheduled delivery

Scheduled delivery turns a report you would otherwise open and export by hand into something that arrives on its own. You pick how often it runs, what time, who receives it, and the file format. Before it goes live, you can fire a one-off test so you know the recipients and format are right.

There are two scopes. A Prism schedule is attached to one Prism — each Prism has at most one schedule, and editing it overwrites the previous one. Mosaic schedules are workspace-level, cron-based, and managed centrally in Lumen, where multiple schedules can target the same Mosaic.

Overview

A schedule answers four questions: how often, at what time, to whom, and in what format.

For a Prism, you configure the schedule from the Prism detail panel. The fields map directly to what Celiq stores:

Saving a Prism schedule upserts it: if the Prism already has a schedule, your new values replace it and the schedule is reactivated. A Prism never accumulates more than one schedule.

For a Mosaic, schedules are listed, toggled on and off, and deleted at Lumen → Schedules. These are cron-based — the recurrence you pick in the form is translated into a cron expression — so they support finer rhythms (hourly, every N minutes, specific days, specific months) in addition to daily/weekly/monthly. Each row shows its recurrence, format, enabled state, and when it last ran.

When to use it

• A stakeholder wants the same report at the same time, repeatedly, and should not have to log in to get it.
• You want a Prism's numbers to land in an inbox or a Slack channel first thing in the morning.
• A Mosaic should be distributed to a recurring audience on a fixed cadence.
• You want to confirm a report renders and reaches the right people before turning the recurring job on — use the test send.

Use a Prism schedule for a single chart or report. Use a Mosaic schedule when the deliverable is a whole dashboard, or when you need cron-level control over the cadence.

Concepts

• Prism schedule — a single recurring delivery bound to one Prism. Stored as one record per Prism; saving again overwrites it.
• Mosaic schedule — a workspace-level, cron-based delivery for a Mosaic. Listed and managed at Lumen → Schedules. A Mosaic can have several.
• Frequency / recurrence — how often the report is sent. Prism schedules use daily, weekly, or monthly; Mosaic schedules additionally support hourly, every-N-minutes, specific days, and specific months via cron.
• Channel — where it is delivered: email, slack, or teams.
• Destination / recipients — for email, a comma-separated list of addresses; for Slack, the channel(s).
• Format — the attachment type: pdf, csv, or excel for Prisms (pdf, csv, png in the unified delivery modal).
• Test send — a one-off delivery that emails the schedule's recipients immediately so you can verify the setup before relying on the recurring run.
• Enabled / active — whether the schedule actually runs. A paused schedule keeps its configuration but does not send.

Getting started

Prerequisites:

• You have a saved Prism (for a Prism schedule) or a Mosaic (for a Mosaic schedule).
• You are a Weaver or Luminary to create or manage schedules.
• For Slack delivery, your workspace's Slack integration is connected and the target channel exists.

To open a Prism schedule, go to the Prism, open its detail panel, and choose Schedule delivery. To manage workspace Mosaic schedules, open Lumen → Schedules at /lumen/schedules.

Step-by-step

For a Mosaic schedule, open Lumen → Schedules, review the existing rows, and use the row controls to toggle a schedule on or off or to delete it. Each row shows the cron-derived recurrence (for example "Every Monday at 09:00 UTC"), the format, and whether it is active.

Examples

A weekly Monday-morning PDF of a sales Prism, sent to two stakeholders by email:

{
  "frequency": "weekly",
  "time_of_day": "09:00",
  "timezone": "UTC",
  "channel": "email",
  "destination": "ceo@company.com, head-of-sales@company.com",
  "format": "pdf"
}

Save this on the Prism, then send a test. The test email arrives with a Test delivery badge, the Prism's name, and the configured frequency and format, plus a link back into Celiq — confirming the recipient list before the schedule runs for real.

A daily CSV dropped into a Slack channel instead:

{
  "frequency": "daily",
  "time_of_day": "07:30",
  "channel": "slack",
  "destination": "#daily-metrics",
  "format": "csv"
}

Best practices

• Always send a test first. It is the fastest way to catch a typo'd address, an empty recipient list, or a wrong format before anyone relies on the report.
• Keep recipient lists current. For email, the destination is a plain comma-separated list — review it when people join or leave the audience.
• Match cadence to how the data updates. A daily send of a monthly metric just creates noise; align the frequency with how often the underlying numbers change.
• Pause instead of deleting. For Mosaic schedules, toggle a schedule off when you only need to stop it temporarily — you keep the configuration for later.
• Use the right scope. One chart or report → Prism schedule. A whole dashboard or a cron-level cadence → Mosaic schedule at Lumen → Schedules.

Tips

Common mistakes

Troubleshooting

Related pages

• Prisms
• Mosaics
• Slack
• Sharing and access