Recurring messages

Create a recurring message

Open your app's Recurring messages section, below Messages.

1. Choose Create recurring message and give it an internal name.
2. Compose the notification. Advanced includes translations, custom data and provider options, as in the regular composer.
3. Select Everyone or a saved audience. Devices must still be opted in and have valid tokens when their send is prepared.
4. Choose daily, selected weekdays, or a monthly day. Last day of the month works in every month; a numbered day missing from a month skips that month.
5. Set a send time in one timezone or in each recipient's timezone. Recipient-local sending requires a fallback timezone for devices without a known timezone.
6. Set the start date and an optional end date. Add tags and an optional device frequency limit.
7. Save draft, check the upcoming dates, then Activate.

An app can have ten recurring messages, including drafts and paused messages. Archive one to free a slot. Tags are copied to each generated message.

Set a device frequency limit

The limit applies only to this recurring message. For example, a daily schedule with a seven-day limit contacts an eligible device at most once in seven rolling 24-hour periods. Other messages and other recurrences are unaffected.

Devices excluded by this limit do not create failed deliveries. The statistics show how many were excluded. An uncertain send outcome consumes the limit to avoid contacting the same device twice; a definite failure does not.

Edit or pause

Edits apply to future occurrences. Each occurrence keeps the content and audience filters it started with, while device eligibility is checked when its timezone wave is prepared. Changes to a saved audience apply to the next occurrence. Deleting that audience blocks future occurrences until you choose another one and resume.

Pause stops future occurrences and pending timezone waves. A send already in flight cannot be recalled. Resume schedules the next future occurrence; it does not catch up missed sends. Archive also stops sending and keeps available history, but cannot be undone.

For recipient-local sending, the next occurrence is the next date whose first possible timezone wave has not started. At a daylight-saving transition, an ambiguous time uses its first occurrence, and a nonexistent time moves to the first valid instant after the gap. Waves delayed by more than fifteen minutes are skipped rather than sent late.

Inspect results

The detail page shows the last thirty days of sent notifications, unique devices contacted, recorded opens, open rate, failures, uncertain outcomes, pending sends and frequency-limit exclusions. Sent means APNs or FCM accepted the message; it does not confirm the device displayed it.

Occurrence history links to each message's delivery trace. History includes occurrences that were created; it does not list every theoretical send during a long pause or outage. Statistics use retained delivery history. See delivery results for interpreting individual outcomes.