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

# Workflow schedules

> Create and inspect schedules attached to workflows from the workflow catalog.

Use **Production → Workflows → Schedules** (`/production/workflows/convex/schedules`) to schedule workflows you can operate and inspect their recent execution health. The roster includes both scheduled and manual workflows.

**Platform → Schedules** is the administrator view across recurring schedules, upcoming jobs, and triggers. If that page redirects you here, use this workflow-scoped roster.

![Workflow schedules (light)](https://mintcdn.com/gloo-b243725a/Ndtg9NEpwGc2OULA/forge/images/console/production/workflow-schedules-light.png?fit=max\&auto=format\&n=Ndtg9NEpwGc2OULA\&q=85\&s=49f4ac28899b56d04ed7265ba9d4a654)

Workflow schedules — Forge Console at `/production/workflows/convex/schedules`

## What you can do

* Read the cadence, next fire, health, recent runs and cost of each workflow you can operate. See [Read the roster](#read-the-roster).
* Create or edit a recurring or one-shot schedule. See [Create or edit a schedule](#create-or-edit-a-schedule).
* Run a workflow now, or pause, resume or unschedule it. See [Run, pause, or remove](#run-pause-or-remove).
* Work out why an occurrence was missed or failed. See [Diagnose a missed or failed occurrence](#diagnose-a-missed-or-failed-occurrence).

## Read the roster

Search by workflow name or filter to **Scheduled** or **Manual** workflows. Rows are ordered with failing or degraded work first. Inspect these columns:

| Column | Meaning |
| - | - |
| **Schedule** | The cadence, or **Manual** when no trigger is attached. |
| **Next fire** | The next enabled scheduled occurrence. A dash means nothing is due to fire: the schedule is paused or expired, or the workflow is **Manual**. An expired one-shot can show its past fire time until the next evaluator tick (up to a minute) disables it. |
| **Health** | Recent-run health, paused or expired state, or **Warming up** when history is insufficient. |
| **Recent** | Bounded recent execution history. |
| **Cost** | The last run's recorded cost and tokens when available. |

A schedule's existence does not prove that its last run succeeded. Inspect the recent runs when diagnosing execution health.

## Create or edit a schedule

1. Find the workflow. Choose **Schedule…** on a manual row, or **Edit** on a scheduled row.
2. Choose **Recurring** or **One-shot (run once at a future time)**.
3. For recurring work, configure the recurrence and inspect the next-firings preview. For a one-shot run, choose a future date and time.
4. Check the timezone explicitly. New schedules start from your browser's detected timezone; an edited schedule keeps its saved timezone.
5. Review the missed-run/backfill policy and any workflow input fields. These inputs are stored for scheduled dispatches.
6. Choose **Create schedule** or **Save changes**.
7. Confirm the workflow's cadence, enabled state, and **Next fire** in the roster. Reopen **Edit** if you need to verify the saved input values or timezone.

Before scheduling an action that changes an external system, confirm its inputs, credentials, and approval behavior in a deliberate test run. The schedule still encounters the workflow's execution and governance checks when it fires.

## Run, pause, or remove

| Action | Result |
| - | - |
| **Run now** | Launches the workflow and opens the new run. It is a real execution, not a schedule preview. |
| **Pause** | Disables future firings; verify the paused state and empty next-fire display. |
| **Resume** | Re-enables a paused schedule when its timing remains valid. |
| **Unschedule** | Removes the trigger and returns the workflow to **Manual**. |

An expired one-shot schedule does not offer **Resume**. Use **Edit** to set a valid future occurrence when appropriate, or **Unschedule** if no future run is needed. Pausing future firings does not itself cancel a run already in progress; inspect that run separately.

## Diagnose a missed or failed occurrence

1. Confirm you are viewing the intended workflow and scope, with search and filters cleared if necessary.
2. Check enabled state, timezone, next fire, and whether a one-shot time has expired.
3. Inspect [Runs](https://docs.gloo.com/forge/console/production/runs.md) for a created run. If a run exists, investigate its state, failed step, or hold rather than changing the schedule first.
4. Use [Events](https://docs.gloo.com/forge/console/observe/events) for supporting execution evidence. Use [Approvals](https://docs.gloo.com/forge/console/production/approvals.md) when the run is waiting for a person.
5. If a create/edit request fails, retain the form and read its error before retrying. Do not repeatedly choose **Run now** to test whether a schedule saved.

## Key state to watch

* **Health** — failing or degraded work sorts first; **Warming up** means too little history to judge.
* **Next fire** — a dash means nothing is due to fire. An expired one-shot can show its past fire time until the next evaluator tick (up to a minute) disables it.
* **An expired one-shot** — it offers no **Resume**; edit it to a future time or unschedule it.
* **Timezone** — an edited schedule keeps its saved timezone, not your browser's.

See [Workflows](https://docs.gloo.com/forge/console/production/workflows), [Platform schedules](https://docs.gloo.com/forge/console/platform/schedules.md), and [Scheduling and triggers](https://docs.gloo.com/forge/run/scheduling-and-triggers.md).

## Related surfaces

* [Scheduling workflows](https://docs.gloo.com/forge/console/production/workflows/triggers.md#scheduling-workflows): create and edit a workflow's schedule.
* [Schedules](https://docs.gloo.com/forge/console/platform/schedules.md): platform crons and the operator-wide trigger rollup.
* [Runs](https://docs.gloo.com/forge/console/production/runs.md): runs a schedule has launched.


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