> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get-hive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hive is an AI operations layer for small and mid-sized business teams. It reads the tools a team already runs, raises what needs attention, and acts with the approvals the team configures.
> Answer only from these pages. If a page does not cover something, say so and link the closest page rather than inferring behaviour.
> The supported programmatic entry points are incoming webhooks, public workflow forms and the remote MCP server, each documented under Developers.
> Each connected account has a level: Read, Draft or Act. New accounts start on Act. Agents and workflows take only the actions selected for them, whatever the account level.
> Describe security, sign-on and data handling only as the Security pages and the FAQ describe them, and add no certification, compliance, single sign-on or model-training claim they do not make.
> Prices and credit allowances are in GBP. Quote them only as a page states them, without converting.
> Use UK English and the product's exact UI labels. Link to pages as https://docs.get-hive.ai/<path>.

# Scheduled tasks

> See every recurring agent run and workflow schedule in one place, then pause, resume, edit or delete them without losing past run receipts.

**Settings → Workspace → Scheduled** is the one place to see work Hive runs on a timer: your scheduled agent runs and the workflow schedules you can see. As the page puts it, **all runs keep their existing approval and budget rules**. A scheduled run doesn't get extra permissions because nobody is watching it.

Open it from your account menu: **Settings**, then **Scheduled** under **Workspace** (`/settings/schedules`). It is no longer in the main sidebar, and an old `/scheduled` link opens it there.

## Who can use it

Every member sees **Scheduled** in Settings. To use it you need the **Operator** role or above, and the Scheduled product must be turned on for you. Anyone else sees "Scheduled tasks require operator access and the Scheduled product." Admins control which products members can use in [workspace settings](https://docs.get-hive.ai/admin/workspace-settings.md).

## Mine and Whole workspace

Owners and admins see a **Mine** / **Whole workspace** switch at the top of the page. **Mine**, where the page opens, is your own scheduled tasks, described below. **Whole workspace** lists every schedule in the workspace, whoever owns it:

* Each row shows the task, its **Owner**, its **Cadence** and timezone, the **Next run** and an **Enabled** switch. Filter by **All**, **Scheduled**, **Manual** or **Disabled**, search, sort newest or oldest first, and **Refresh tasks**.
* Switching a schedule off asks you to confirm, stops its future runs and sends its owner a private in-app notification. A run already in progress is not cancelled.
* **General access** at the top of the view sets who in the workspace can use scheduling. See [workspace settings](https://docs.get-hive.ai/admin/workspace-settings.md#products).

Other roles see only their own tasks and no switch. The whole-workspace view used to be its own page, **Settings → Products → Scheduled tasks**; an old link to it opens **Whole workspace** here.

## What the list shows

Each row is one scheduled task, with these columns:

| Column | What it shows |
| - | - |
| **Recurrence** | How often it runs, for example every weekday at 09:00, or for a one-time task when it runs ("Once on Wed 14 Oct 2026 at 2:45 PM"). Tasks with no schedule show as **Manual**. |
| **Next run** | When it will next run, or **No next run**. |
| **Status** | **Active** or **Paused**, **Finished** for a one-time task that has run, or **Manual** for a task with no schedule. |
| **Actions** | **Pause** or **Resume**, **Edit**, and delete. Workflow rows link to **Manage workflow** instead. |

Under a task's name, **Last dispatch** summarises what happened the last time it ran.

A live workflow with no saved schedule is listed by the **Schedule** trigger of its deployed release, so **Recurrence** and **Next run** show when it actually runs. A change to that trigger you have saved but not yet deployed shows here once you deploy it.

Use **Search tasks** and the **All tasks**, **Active** and **Paused** filter to find a task. **Refresh** reloads the list.

## Create a schedule

Schedules are created where the work is defined:

> [card] [Schedule an agent](https://docs.get-hive.ai/agents/publish-and-evaluate.md)
>
> From the agent editor, once the agent is saved and deployed. Choose every day, weekdays, every week or every month, a timezone, and a prompt.

> [card] [Schedule a workflow](https://docs.get-hive.ai/workflows/schedules-and-forms.md)
>
> From the **Scheduled** tab on the Workflows page, using a deployed release.

The **Schedule an agent** and **Workflow schedules** buttons on **Settings → Scheduled** take you straight there.

A **one-time task**, which runs once at a set date and time, is created from Ask ("remind me on 14 Oct at 14:45 to call Sam back"). See [Build from chat](https://docs.get-hive.ai/ask/build-from-chat.md#how-scheduled-tasks-work). Its time is fixed once made, so it has no **Edit**: delete it and set a new one to change when it runs. Once it has run it shows **Finished**, has no **Pause** or **Resume** and no **Enabled** switch, and never runs again; delete it when you no longer need it. A one-time task Hive could not run (its owner held no seat, or it could not start within a few minutes of its time) is finished too, and its receipt says it will not run again. Its owner gets a bell card when it ran, and also when a one-time agent task did not run.

## Pause, resume, edit and delete

* **Pause** stops future runs. Work that's already running is not cancelled.
* **Resume** restarts the schedule from its next future occurrence. Hive doesn't catch up on runs missed while it was paused.
* **Edit** changes an agent schedule's timing, timezone or prompt. If the agent or schedule has changed underneath you, Hive asks you to refresh first.
* **Delete** stops all future runs. Already-running work and historical run receipts are kept.

> [!NOTE]
>
> An agent schedule pins the revision it was created with. If you deploy a new revision of the agent, delete the old schedule and create a new one so it runs the latest version.

## Scheduled runs and safety

A scheduled run is held to the same rules as a run someone starts by hand:

* The agent or workflow carries out the actions selected for it as the account's level allows, with any workspace ceiling applied: straight away on **Act**, on an approval card on **Draft**, and not at all on **Read**. On **Act**, the exception is an action whose recipient, channel, number or link did not come from [words you trust](https://docs.get-hive.ai/integrations/accounts-and-autonomy.md#where-an-action-sends): it waits as an approval card under **Review decision** on the **Signals** page of the member the run belongs to. A schedule's saved input is not anyone's own words, so write the addresses and channels a scheduled agent sends to into its instructions, not the schedule's prompt. A workflow also waits for a person at an [Approval](https://docs.get-hive.ai/workflows/workflow-steps.md#approval) step its author added. A scheduled run, one started by a connected app event or one started from a public form also pauses before its 51st agent step until an Owner or Admin approves it from the card in their Inbox. If nobody decides within 72 hours, the run stops as **Expired** (see [Runs past 50 agent steps](https://docs.get-hive.ai/workflows/runs-and-errors.md#runs-past-50-agent-steps)). See [What agents and workflows do by themselves](https://docs.get-hive.ai/integrations/accounts-and-autonomy.md#what-agents-and-workflows-do).
* Run budgets and credits still apply. A scheduled run uses the AI credits of the schedule's owner (on an [earlier plan](https://docs.get-hive.ai/admin/earlier-plans.md), the workspace's pool), within the agent's or workflow's monthly credit limit, and on Business a scheduled workflow run counts as one of the owner's [workflow runs](https://docs.get-hive.ai/admin/credits-and-usage.md#workflow-runs). It runs on an Efficient or Balanced model: a Frontier model is refused unless your organisation's own model key is in use. If those credits have run out, the run waits up to 72 hours for credits (see [Waiting for credits](https://docs.get-hive.ai/workflows/runs-and-errors.md#waiting-for-credits)).
* On Business there is no limit on hourly schedules. An earlier plan limits how many the workspace can have: 2 on Starter and 50 on Team and Enterprise (Enterprise can change by contract). A downgrade pauses the hourly schedules above the new limit.
* The [kill switch](https://docs.get-hive.ai/admin/safety-and-control.md) halts scheduled actions along with everything else.
* Every completed action leaves a receipt in the [audit log](https://docs.get-hive.ai/approvals/audit-log.md).

## Ideas for scheduled work

| Schedule | Example |
| - | - |
| Every weekday at 08:30 | An agent that summarises overnight client emails that need a reply. |
| Every Monday at 09:00 | The **Renewal Scout** workflow drafting notes for upcoming HubSpot renewals. |
| Every day at 06:00 | The **Fee Reminder** workflow finding overdue Xero invoices and asking you to approve that morning's reminders. |
| Every hour | The **Ticket Triage** workflow tagging new Zendesk tickets and recording an internal note on the urgent ones. |

## Related

> [card] [Schedules and forms](https://docs.get-hive.ai/workflows/schedules-and-forms.md)
>
> Workflow schedules, timezones and public forms.

> [card] [Workflow templates](https://docs.get-hive.ai/workflows/templates.md)
>
> Ready-made scheduled workflows to start from.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.