Schedule gates

Quiet hours that still let real outages through.

A schedule gate only lets a flow continue during hours and days you set, in your timezone. Put the noise behind it and leave the critical path ungated, so nothing urgent is ever held back.

Per step, not per account. The gate sits on one branch of one policy, so it never becomes a global switch that silences everything.
Overnight windows supported. A window can cross midnight, which is what most out-of-hours rules actually need.
Your timezone, not UTC. Hours are evaluated in the timezone you set, so a rule written as working hours stays working hours.

Start free All features

01 · What it does

A door on one branch of the flow.

The gate is a logic module like any other. Anything downstream of it only runs inside the window.

Set hours and days

Choose the window and the days it applies to. Outside it, the steps behind the gate simply do not run.

Overnight windows

A window that crosses midnight is supported directly, so an out-of-hours rule does not need to be split into two.

Timezone aware

The window is evaluated in the timezone you set rather than UTC, so it means what it says all year round.

Gate anything downstream

Notifications, actions and further branches behind the gate are all held together, so one module controls a whole path.

02 · How to use it well

Two paths, not one switch.

The mistake is gating everything. The pattern that works is branching first, then gating only the branch that can wait.

Keep the critical path open

Draw the urgent branch straight to a page with no gate on it. A payment API going down at 2am should always reach someone.

Gate the informational branch

Send routine notices to a channel only during working hours, so nobody wakes to a message about a background job.

Business hours support alerts

Route alerts for services that only matter while people are working to a gate that matches the office day.

Weekend behaviour

Set different days on the gate so a weekday-only service stops generating chatter on Saturday.

Combine with the on-call rota

Gate the channel notification and leave the rota-following page ungated, so the on-call engineer is reached whenever the rota says so.

Pair with noise controls

A gate decides when an alert may fire. Confirmation thresholds and dampening decide whether it should fire at all.

Questions

Common questions

Do schedule gates silence all my alerts outside working hours?

Only the ones you put behind them. A gate sits on one branch of one policy, so the normal pattern is to branch first and gate only the path that can wait, leaving the critical path open around the clock.

Can a schedule window run overnight?

Yes. Windows that cross midnight are supported directly, so a rule covering something like 18:00 to 08:00 does not need to be split into two separate gates.

Which timezone are the hours evaluated in?

The timezone you set. Hours are not evaluated in UTC, which means a window written as working hours continues to mean working hours after the clocks change.

What is the difference between a schedule gate and a maintenance window?

A gate controls when an alert is allowed through while the monitor keeps checking normally. A maintenance window pauses the monitor itself during planned work, so no incident is recorded at all.