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

# Schedules

> View, activate, and deactivate the timers and workflow schedules that start process instances and workflow runs, without redeploying the build.

## Overview

The **Schedules** page (**Runtime** → **Runtime Settings** → **Schedules**) lists the Timer Start Events that start process instances and the workflow schedules that start workflow runs. You can view them and activate or deactivate them without a redeployment. This feature is especially useful in upper environments, where you might need to pause or resume cron jobs without modifying the project build.

> [card] [Timer Start Event](https://docs.flowx.ai/6.x/docs/building-blocks/node/timer-events/timer-start-event.md)
>
> Check this section for more details about Timer Start Events and how to configure them.

![Scheduled processes list in Runtime Settings with State, Process Name, Swimlane Name, Timer Name, Timer Type, and Location columns, including one row per swimlane for a multi-swimlane process](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/4.6/scheduled_processes.png)

### Where are workflow schedules managed?

This page is called **Schedules** (**Runtime** → **Runtime Settings** → **Schedules**). It lists process timers and [workflow schedules](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/integration-designer.md#how-do-i-run-a-workflow-on-a-schedule) together, and the **Origin** filter (**Process** or **Workflow**) separates them. You activate and deactivate workflow schedules here the same way as process timers.

## Key components

### 1. List of schedules

The **Schedules** page displays every process timer and workflow schedule. Each row in the list shows:

* **State:** Whether the schedule is active.
* **Origin:** **Process** for a Timer Start Event, **Workflow** for a workflow schedule.
* **Name:** The process or workflow the schedule starts.
* **Schedule:** The name of the timer node or of the workflow schedule.
* **Type:**
  * **Date:** Triggers at a specific date and time.
  * **Cycle:** Repeats at defined intervals (for example, every 10 seconds).
* **Location:** **Local**, or the name of the dependency the schedule comes from.

In multi-swimlane processes, each swimlane may have its own timer, and each one gets its own row. Use **Filter by origin** to show only process timers or only workflow schedules, and the search box to find a schedule by name.

From this interface, you can view schedule details or activate and deactivate schedules as needed.

### 2. Schedule details

To view a schedule's configuration, click the **View** icon next to it in the list. The **Schedule details** dialog shows the process or workflow, the swimlane of a process timer, the schedule name, the location, the expression, and the next fire times.

![Timer Events Schedule dialog for a Cycle timer showing Repeat Every 10 secs and 60 repeats](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/4.6/timer_events_schedule.png)

### 3. Activating and deactivating schedules

Manage timer activation directly from the UI:

![Animation of activating a timer from the play icon in the Scheduled processes list](https://s3.eu-west-1.amazonaws.com/docx.flowx.ai/4.6/activate_scheduled_processes.gif)

* **Activate:** Click the **Activate** button on the schedule's row, then confirm. The confirmation lists the next fire times and warns you when the schedule has none.
* **Deactivate:** Click the same button, now **Deactivate**, and confirm to suspend the schedule.

> [!WARNING]
>
> You cannot edit schedule configurations in the **Runtime** tab. To modify settings, update the process definition or the workflow and redeploy.

***

## Use cases

**1. Employee Onboarding reminder**

A Timer Start Event can be scheduled to **automatically trigger** an onboarding process at a predefined time.

**Example**: Process starts on **January 28, 2025, at 12:14 PM**, sending onboarding notifications.

**2. Recurring Data processing jobs**

A Cycle timer can execute a job **every 10 seconds for 60 repetitions**, ensuring periodic execution.

**3. Scheduled Report generation**

A cycle timer with a cron expression can generate a report at **1 AM every day**.

***

## Additional notes

* **Runtime Timer Control:**\
  Manage timers in the **Runtime** tab without changing the application build. The Timer Start Event node itself has no activation setting.

* **Timers in Multi-Swimlane Processes:**\
  Each swimlane can have its own timer. The **Schedules** page displays each timer separately for clear management.

* **Exporting and Importing Builds:**\
  Timer activation settings are not editable during build export/import. All timer management occurs in the **Runtime** tab.

***

## Related resources

> [card] [Timer Start Event](https://docs.flowx.ai/6.x/docs/building-blocks/node/timer-events/timer-start-event.md)
>
> Configure the Date or Cycle timer that schedules a process

> [card] [Timer expressions](https://docs.flowx.ai/6.x/docs/building-blocks/node/timer-events/timer-expressions.md)
>
> ISO 8601 and cron syntax for timer definitions

> [card] [Active policy](https://docs.flowx.ai/6.x/docs/projects/runtime/active-policy.md)
>
> Choose the build whose timers are scheduled


## Related topics

- [Scheduler setup](https://docs.flowx.ai/6.x/setup-guides/scheduler-setup-guide.md)
- [FlowX.AI Scheduler](https://docs.flowx.ai/6.x/docs/platform-deep-dive/core-extensions/scheduler.md)
- [Integration Designer](https://docs.flowx.ai/6.x/docs/platform-deep-dive/integrations/integration-designer.md)
- [FlowX.AI 6.0.0 Release Notes](https://docs.flowx.ai/release-notes/v6.x/v6.0.0-october-2026/v6.0.0-october-2026.md)
- [Task management setup](https://docs.flowx.ai/6.x/setup-guides/task-management-plugin-setup.md)


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