Support multiple cron expressions (or multiple Schedule triggers) for a single task

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

Support multiple cron expressions (or multiple Schedule triggers) for a single task

Problem

Currently, a task can only have a single cron expression.

While cron is very expressive, many perfectly valid schedules cannot be represented with a single expression because the minute field is shared across all specified hours.

For example, suppose I want a task to run at:

• 15:03
• 17:04
• 19:45

These schedules require three different cron expressions:

3 15 * * *
4 17 * * *
45 19 * * *

The only workaround today is to create multiple identical tasks that differ only in their schedule.

Benefits

• Avoids creating duplicate tasks.
• Makes schedules much easier to maintain.
• Supports arbitrary schedules that cannot be represented with a single cron expression.
• Keeps all executions for the same task grouped together.

Proposed Solution

Proposed solution

Allow a task to have multiple cron expressions.

For example:

3 15 * * *
4 17 * * *
45 19 * * *

This feels like a natural extension of the current UI, since there is already an "Add another trigger" action, but it currently only supports different trigger types (GitHub, API, etc.), not additional schedule triggers.

Alternative Solutions

Or, even better, allow adding multiple Schedule triggers to the same task, similar to how other trigger types can already be added.

Example:

Task
├── Schedule
│     3 15 * * *
├── Schedule
│     4 17 * * *
└── Schedule
      45 19 * * *

Priority

Medium - Would be very helpful

Feature Category

Configuration and settings

Use Case Example

Use Case Example

Example scenario:

1. I have a single automation that sends different reminders throughout the day.
2. The reminders should run at:

• 09:03
• 14:15
• 17:42
• 19:45

1. These execution times cannot be represented with a single cron expression because they require different minute values.
2. Today, I have to create multiple identical tasks that only differ by their schedule.
3. With support for multiple Schedule triggers (or multiple cron expressions), I could keep all of these schedules within a single task.
4. This would make the configuration easier to maintain, avoid duplication, and ensure changes to the task only need to be made once.

Additional Context

Additional Context

Current behavior

A task only accepts a single cron expression.

For schedules such as:

3 9 * * *
15 14 * * *
42 17 * * *
45 19 * * *

the only option is to duplicate the task four times, even though the task logic is identical.

Proposed UI

Since the UI already supports "Add another trigger", it would be intuitive to also allow adding additional Schedule triggers.

Example:

Task
├── Schedule
│     3 9 * * *
├── Schedule
│     15 14 * * *
├── Schedule
│     42 17 * * *
└── Schedule
      45 19 * * *

Alternatively, allow multiple cron expressions within the same Schedule trigger.

Related

• Related feature request: https://github.com/anthropics/claude-code/issues/50529

That feature addresses timezone support, while this proposal addresses a different limitation: expressing schedules that require multiple cron expressions.