Scheduled Tasks

Scheduled Tasks let you run tasks on a schedule — or whenever you need them. Save a natural-language prompt for the agent and have Cube run it automatically on a schedule or on demand. Each run produces a chat thread you can open later to read the agent’s answer. You can also ask the agent to create a scheduled task for you from any of your chats. For example, you might schedule a task to “every weekday at 9am, summarize yesterday’s signups, flag anything anomalous, and email me the results” and review the summary each morning. Scheduled Tasks are scoped to a deployment — each task belongs to the deployment it was created in.

​

Where to find it

In the deployment sidebar, open Scheduled (the clock icon, below Explore). The page lists the deployment’s tasks with their name, schedule, status, and description, and is searchable.

​

Anatomy of a task

A task has:

• Name (required) — how the task appears in the list.
• Description (optional) — a short summary shown in the list.
• Instructions (required) — the natural-language prompt the agent runs on each execution.
• Schedule — how often the task runs (see below).
• Enabled — a toggle to activate or pause a scheduled task.

​

Schedule options

Scheduled Tasks use the same schedule editor as dashboard scheduled refresh, offering these frequencies:

• Manual — no schedule; the task runs only when you trigger it with Run now.
• Hourly, Daily, Weekly (with a day of the week), and Monthly (with a day of the month) — each with a time picker.
• Custom — a raw five-field cron expression. Its minute field must be a single number, so it fires at most once an hour: 30 9 * * 1-5 (9:30 on weekdays) works, while */15 * * * * is rejected.

A timezone selector (defaulting to your browser’s timezone) controls when the schedule fires; it is stored per task.

​

Limits

Each user can have up to 20 active tasks across all of the account’s deployments, where active means scheduled and enabled. Manual and paused tasks don’t count toward this limit. At the limit, anything that would make a task active fails: creating a scheduled task, resuming a paused one, or adding a schedule to a Manual task. Pause or delete another task first, or keep the new one Manual. The Scheduled page lists one deployment’s tasks, so active tasks you created in other deployments count toward the limit without appearing there. Check the Scheduled page of each deployment you work in to find them.

​

Managing tasks

Anyone who can use the deployment can see its tasks and create new ones. Only a task’s creator, or a user with the Admin role, can edit, pause, run, or delete it, because every run executes as the creator (see Reading the output). The admin exception carries the creator’s data access with it: an admin who edits another user’s task changes what runs under that user’s access. A run’s chat thread belongs to the task’s creator, and only the creator, admins, users with the Access chat history permission, and people it’s shared with can open it. From the list, you can:

• Create a new task. The New task button is a dropdown with two options:
  • Create with agent — opens a new Analytics Chat pre-seeded with a message asking the agent to explain scheduled tasks and interview you about what the task should do and when it should run. The agent then creates the task for you (see Managing tasks from chat).
  • Set up manually — opens the create dialog where you fill in the task’s details yourself.
• Edit an existing task’s instructions, schedule, or details.
• Enable / Pause a scheduled task to control whether it runs on schedule.
• Run now — trigger a one-off run immediately. This works for both manual and scheduled tasks. Triggering a run shows a notification with a View link straight to the run’s chat thread, and the thread appears in the Recent Chats sidebar immediately.
• Delete a task. Deleting removes its schedule and stops all future runs.

​

Task detail page

Clicking a task in the list opens its detail page. The header shows a breadcrumb back to Scheduled Tasks, the task name, a status tag (Manual, Active, or Paused), and the description, along with actions to Edit (pencil), Delete (trash), and a primary Run now button. The page shows:

• History — the task’s runs, newest first. Each entry is a timestamped link that opens that run’s chat thread, if you can access it. Currently-executing runs show a Running tag, and failed runs a Failed tag. The list shows the latest 50 runs; a “Showing the latest 50 runs” note appears once the cap is hit.
• Instructions — the task’s prompt.
• Repeats — the schedule in plain language.

​

Reading the output

Each run creates a chat thread containing the agent’s response. Open the thread in Analytics Chat to read the full answer, ask follow-up questions, or save results to a Workbook. Scheduled-run threads are marked in the Recent Chats sidebar with a clock icon (hover over it to see the “Scheduled task” tooltip). A run shows as Running while it executes, then completes or fails. A failed run’s thread shows a failure notice instead of an empty thread. A run’s thread carries no memory of earlier runs, so write the Instructions as a complete request rather than a follow-up to the last run. The task runs headlessly under the security context of the user who created it, so it sees exactly the data that user can access.

​

What the agent can do in a scheduled run

Beyond querying the semantic model, the agent in a scheduled run can:

• Send email to workspace members — for example, “summarize yesterday’s signups and email the summary to me.” This requires the agent email tool to be enabled for the workspace; recipients are restricted to workspace members.
• Use web search.
• Create and update reports, workbooks, and dashboards, using the task creator’s permissions.

Scheduled runs do not yet have data-model access — editing the semantic layer is currently available only in interactive chat.

​

Managing tasks from chat

You can also create and manage Scheduled Tasks conversationally in Analytics Chat — from any chat, not just ones started with Create with agent (that menu option simply opens a chat pre-seeded for this flow). Ask the agent to schedule, update, list, or delete tasks in plain language — for example, “schedule a daily summary of yesterday’s signups at 9am” or “list my scheduled tasks.” The agent’s actions render in the chat as labeled steps with a clock icon — “Creating scheduled task…” / “Created scheduled task”, “Listed scheduled tasks”, “Updated scheduled task”, and “Deleted scheduled task”. The agent manages task definitions: when listing tasks, it can report each task’s id, name, description, schedule, timezone, enabled state, and next run time. A task’s run history lives on its detail page. The agent follows the same limits and permissions as the Scheduled page, and a scheduled run can’t create or change tasks itself.

​

Managing tasks with the Platform API

You can also create, update, pause, run, and delete Scheduled Tasks from scripts and CI with the Platform API (by default, only admins can create API keys). Its Scheduled Tasks endpoints follow the same limits and permissions as the Scheduled page. See the API reference for the endpoints, fields, and responses.