Routing and destinations

Notification timing

Use immediate notices, fixed batch windows, and quiet hours without delaying mailbox arrival.

When to use it

Batch related arrivals when fewer interruptions help, or hold notices during your local overnight quiet hours.

Example

A two-minute batch starts at its first pending arrival. Mail arriving exactly at its cutoff enters a later window. Quiet hours hold completed windows until morning without moving their cutoffs.

Set it up

  1. In Mailboxes, select a mailbox and open Configure > Triggers to choose timing, or have an approved admin use save_mailbox_trigger.
  2. Use timing.mode immediate for the default, or batch with windowSeconds from 30 to 3,600.
  3. For quiet hours, set timing.quietHours with an IANA timeZone and nonoverlapping periods of start and end times. Overnight periods are allowed; leave time for delivery.
  4. Review the saved settings. Send fresh matching activity and inspect each destination's due time and outcome.

Important limits

  • The same timing applies to email, webhooks, MCP, Slack, Teams, and internal sends. Immediate is the default.
  • A fixed batch begins at its first pending arrival. Later arrivals do not move its cutoff. Arrivals at or after the cutoff belong to a later window.
  • Quiet hours hold notices, not mailbox mail. Completed held windows combine only for the same mailbox, trigger revision, and destination. A still-open window waits for its own cutoff. Immediate-mode arrivals held by quiet hours combine without a batch delay.
  • Before the first attempt, the notice freezes its delivery identity, activity, and window references. Retries keep them unchanged and never merge later arrivals.
  • Timing neither discards mail nor extends its seven-day lifetime. Reading or organizing mail does not change notice delivery.
  • Edits apply to later arrivals. Pausing a trigger cancels unsent work; resuming does not notify about skipped arrivals. In-flight requests may finish.

Troubleshooting

  • Use mailbox_delivery_status for related due times under mailbox access. Admins can call get_notifier_diagnostics with id set to the trigger's notifierId.
  • If the delivery time is wrong, check the saved IANA time zone, quiet-hour boundaries, and fixed window cutoff.
  • If a retry repeats, compare deliveryId and activityIds. A retry is the same handoff, not new mail or a new execution request.
Open Agent Doorbell