Skip to content

Clarify Linked Audiences run schedule behavior and execution timing #8052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 16, 2025
Merged

Clarify Linked Audiences run schedule behavior and execution timing #8052

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
082307b
Update linked-audiences.md
maleman842 Oct 15, 2025
875a7d0
minor rewording [netlify-build]
pwseg Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions src/engage/audiences/linked-audiences.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -248,13 +248,15 @@ Determine when an audience should run and send data to enabled destinations with

You can maintain your run schedule at any time from the audience's **Settings** tab.

> info "Run schedule timing"
> Interval run schedules are based on UTC time using a cron-style system. This means the next run time aligns with the nearest UTC interval, which may differ from your local time. For example, if you set a 24-hour interval at 4 PM PST, the next run aligns with 12 AM UTC, which occurs at 5 PM PST. If you set it after 5 PM PST, the next run occurs the following day at 5 PM PST.

You can also click **Run Now** on the Audience Overview page at any time (even if the run schedule is **Interval** Overview **Day and time**) to manually trigger a run on your warehouse and send data to enabled destinations.

There may be up to a five minute delay from the configured start time for audiences that are configured with the **Interval** and **Day and time** run schedules. For example, if you configured an audience with the **Day and time** compute schedule to run on Mondays at 8am, it can compute as late as Monday at 8:05am. This is to help us better manage our system load.

> info ""
> When configuring an interval run schedule, the system uses a cron-based mechanism anchored to UTC, meaning the next run time aligns with the nearest UTC-based interval cycle, which may shift the schedule relative to your local time zone.
> When you set a 24-hour interval run schedule at, for example, 4 PM PST, the cron-based system using UTC schedules the next run for 5 PM PST the same day, as it aligns with 12 AM UTC; however, if set after 5 PM PST, the next run will be at 5 PM PST the following day.
> info "Execution timing"
> Linked Audiences don’t schedule the next run until the current one finishes. For example, if you set a 15-minute interval but the workflow takes an hour to complete, the next run won’t start until that hour-long run ends. After it finishes, Segment calculates the next run time based on the next available interval.

## Step 5: Monitor your activation

Expand Down
Loading