While creating a campaign, select Recurring Frequency to run it automatically at regular intervals. Use this option when you want the same message to be delivered repeatedly-such as weekly updates, monthly reminders, or ongoing notifications without having to recreate or resend the campaign each time. When selected, you can define the frequency and timing so the campaign is sent consistently based on the chosen schedule.
In the Frequency section, select the Recurring card.
The Recurring card is highlighted and the One-Time card is dimmed (not selected).
In the Schedule row select the start date and end date when the campaign is allowed to run.
Select the Start Date field or its calendar icon to open the date picker. In the calendar, use the month and year controls to navigate if needed, then select the required day.
The date picker closes and the chosen date is displayed in the field in MM/DD/YY format (for example, 07/27/26).
Repeat this action for End Date. After you select a day from the date picker, the end date is also displayed in MM/DD/YY format (for example, 07/31/26).
Configure Run Frequency Using Natural Language
In the Run Frequency box, place the cursor in the text area.
Type a clear natural-language instruction that describes when the campaign should run.
For example: 23:00 everyday
After you type the instruction, the Set Schedule button becomes active.
Select Set Schedule. The AI interprets your instruction and automatically populates the schedule details:
Frequency – Everyday
Time – the execution time (for example, 11:00 PM)
Timezone – the timezone parsed from your text (for example, Asia/Calcutta)
Local Time – the equivalent local time based on your local settings
Review the Run Frequency summary text (for example, “Run Everyday at 11:00 hours”) and the table values to confirm they match your intent.
To update the run frequency later, select Update Schedule.
This makes the Run Frequency text area editable again.
Modify the natural-language instruction and select Set Schedule so that Frequency, Time, Timezone, and Local Time are refreshed with the new pattern.
Additional safeguards have been introduced to improve the stability and predictability of background processing:
Campaign scheduling is now limited to a minimum interval of every 3 hours, preventing overly frequent execution.
Alerts are generated when jobs fail.
New checks prevent triggering additional imports while existing jobs are still running.
Pagination has been introduced for in-queue job lookups to better handle larger workloads.