Choose schedule timing, time zones, and maximum runs

Scheduled Tasks can repeat supported AI Tool inputs or a saved Joule prompt. The timing controls decide when that work starts, which timezone Ampere uses, and whether the task should stop after a set number of runs.

Saving or reviewing a schedule does not spend credits. Credits are used when the AI Tool or Joule run starts.

Know which timing options apply

The current scheduling controls support:

• Hourly: run once every hour at a selected minute.
• Daily: run once every day at a selected time.
• Weekly: run on one or more selected days at a selected time.
• Monthly: run on a selected day of the month at a selected time.
• Manual: keep a saved Joule task ready for Run now without automatic runs.

The exact choices depend on where you create the task. Supported AI Tool flows expose recurring schedules. The Joule task dialog also supports Manual. One-time work that does not need to be saved should usually stay in the current Joule chat.

Choose the schedule and time

Select the schedule type first. The fields below it change for the cadence you choose.

• For hourly tasks, choose the minute past the hour.
• For daily tasks, choose the time of day.
• For weekly tasks, select at least one day and a time.
• For monthly tasks, choose a day of the month and a time.

The picker uses 15-minute scheduling precision, with :00, :15, :30, and :45 minute choices.

For a manual Joule task, no next scheduled time is calculated. Select Run now whenever you want an execution.

Understand monthly last-day behavior

If the selected monthly day does not exist in a shorter month, Ampere runs the task on that month's last day.

For example, a task set to day 31 runs on February's last day rather than being skipped. The task summary and next-run time use this same rule.

Choose the timezone

The task dialog starts with your browser timezone. Change it when the task should follow a team's operating timezone, a market's local time, or another calendar.

The saved timezone remains part of the task. If a teammate in another timezone opens the task, review the explicit saved timezone and next-run value instead of assuming the time was converted to their local preference.

Daylight-saving changes follow the saved timezone. Check the next-run value around a clock change when the exact local hour matters.

Set a run limit

Open Advanced settings or Advanced options and find the run-limit field. The label can vary by task flow, but the behavior is the same:

• Leave it blank for ongoing work.
• Enter a positive number when the task should stop automatically after that many runs.

Examples:

• No limit for an ongoing weekly competitor brief.
• 5 runs for a five-day launch review.
• 12 runs for a monthly task that should last one year.

When the run count reaches the limit, the task completes instead of scheduling another run. Review its details before changing or extending the limit.

Review failure-pause settings separately

A run limit is not the same as Pause after repeated failures. The run limit ends the task after the planned number of runs. The repeated-failure setting pauses it when consecutive runs fail.

Before resuming a failure-paused task, review the latest error, saved prompt or inputs, project access, credits, and any approval state.

Confirm timing before saving

Review:

1. Whether this should be an AI Tool task or a Joule task.
2. The cadence and selected days.
3. The exact time and 15-minute slot.
4. The saved timezone.
5. The monthly fallback if the chosen day can be absent.
6. The optional run limit and repeated-failure pause threshold.

After creation, open the Scheduled Tasks dashboard to confirm the status, saved schedule, timezone, and next run. If the displayed next run is not what you intended, edit the task before the first automatic execution.