RedFlare

Schedules

RedFlare doesn't have a separate Schedules area you visit on its own. Instead, scheduling shows up in the two places where it makes sense to run something on a repeating cadence: inside an alert and inside a workflow. In both, you pick how often and when, and runs fire in your timezone.

This page is a reference for those recurrence controls, so you can set them confidently wherever you meet them.

Where you set a schedule

  • In an alert. When you create or edit an alert, one step is Schedule Type (shown as Schedule & Recurrence). This is where you decide how often the alert checks your conditions and fires. See Alerts.
  • In a workflow. When you choose the On a Schedule trigger, you set the same timing controls so the whole workflow runs on a repeating cadence. See Workflows.

The controls are the same in both places, so once you've set one, the other will feel familiar. You pick how often and when; runs fire in your timezone.

Choose your timezone

Set the Timezone first. It answers "What timezone should this run in?" so every run fires at the right local time, even across daylight-saving changes. A run set for 8am always lands at 8am where you are.

Pick how often it repeats

Set Schedule starts on to choose the date it begins, then pick a Recurrence to control how often it repeats:

  • Once for a single, one-time run.
  • Daily.
  • A weekly option, such as Weekly on Monday.
  • A monthly option, such as the second Saturday of the month.
  • An annual option, such as Annually on 11th October.
  • Every weekday (Monday to Friday).
  • Custom to build your own cadence.
  • CRON for a precise expression.

For most recurring options you also set a Trigger time for when each run fires. If you pick Once, you set a single Trigger date and time instead.

Choosing Once turns it into a single, one-time run. Every other recurrence keeps repeating until it reaches the end rule you set.

Build a custom cadence

When the presets don't fit, choose Custom to shape the cadence yourself.

  1. Under Repeat every, enter a number and pick a unit: hour, day, week, month, or year.
  2. If you repeat by week, use Repeats on to choose which days, then set the time under At.
  3. If you repeat by day or hour, set the time the run should trigger.
  4. If you repeat by month or year, use Repeats on to choose a fixed date or a relative day (such as "the second Saturday"), worked out from your start date.

Hourly custom schedules use clean intervals like every 2, 3, 6, 8, 12, or 24 hours, so runs spread evenly across the day.

Decide when it ends

Every recurring schedule needs an end rule. Under Schedule recurrence ends ("When should the recurring schedule end?"), choose one:

  • Never keeps it running indefinitely.
  • On stops it on a specific date you pick.
  • After running for a set number of times stops it once it has run that many times.

If you're testing a new cadence, set it to end After running for a small number of times. You'll see how it behaves without committing to something that runs forever.

Use a CRON expression

For full control over timing, choose CRON and enter a CRON expression. RedFlare uses it directly, so you can express patterns like:

  • 9am and 5pm daily
  • 8am weekdays
  • Every 30 minutes during work hours
  • 10:15am every day

If you're new to the syntax, start from a simple pattern (such as a fixed time each day) and adjust from there. Your timezone still applies, so the expression is read in the local time you selected.