Schedule Profile Reports
Configure and change the UTC schedule used by an Information Operations profile.
Every active custom profile stores a UTC cron schedule. Y2 uses it to enqueue the next report run after the current run reaches a terminal state.
Supported frequencies
| Frequency | Current schedule behavior | Required input |
|---|---|---|
| Daily | Every day at the selected UTC time | Time |
| Weekly | Every selected weekday at the selected UTC time | Weekday and time |
| Biweekly | On the 1st and 15th of each month at the selected UTC time | Time |
| Monthly | On the selected day of the month at the selected UTC time | Day of month and time |
Biweekly means twice monthly
The current Biweekly schedule runs on calendar days 1 and 15. It is not a rolling fourteen-day interval and does not use the weekly day selector.
Monthly dates 29–31
A monthly schedule runs only when the selected date exists. For example, a profile scheduled for the 31st does not run in a thirty-day month.
Set a schedule
Open the profile editor
Open My Profiles, select the profile, and choose its edit action.
Open Advanced Configuration
Move to the third editor step. Find Delivery Schedule at the top of the page.
Choose a frequency
Select Daily, Weekly, Biweekly, or Monthly. Weekly adds a weekday selector; Monthly adds a day-of-month selector.
Choose the UTC time
Select an hourly time from 00:00 through 23:00. The editor and backend interpret the value
as UTC.
Convert the desired local time to UTC before saving. Repeat the conversion when your local timezone enters or leaves daylight saving time.
Save and verify
Select Update Feed, return to My Profiles, and confirm that the profile displays the expected next-run information.
Schedule edits start an immediate run
Changing the schedule of an active profile cancels its existing scheduled job, enqueues the new schedule, and starts a report workflow immediately. Make schedule changes when an extra run is acceptable.
Generated cron values
Y2 generates the cron expression; the profile editor does not accept a custom expression.
Prop
Type
Choose an effective cadence
Daily
Use for topics where a missed day changes the decision: active incidents, market movement, or operational disruptions.
Weekly
Use for recurring reviews where developments should accumulate into a manageable briefing.
Biweekly
Use when twice-monthly calendar reporting is acceptable and strict fourteen-day spacing is not required.
Monthly
Use for slower trend reviews, executive summaries, or stable watch areas.
When several profiles serve the same reader, stagger their UTC times. This spreads research work and prevents multiple reports from arriving together.
Failure and recovery behavior
Report workflows use bounded action retries and a recovery watchdog for eligible interrupted or stalled runs. A failed synthesis does not proceed to audio or delivery as if it were complete. Recovery behavior does not change the profile's stored cadence.