Campaign Execution Cycle
The life cycle of the Campaign execution (i.e. running) stage depends on the individual execution cycles for each of its configured engagement types. Once each of these types have completed their execution cycles, the Campaign moves to the wrap-up stage.
The system generates the execution schedule for the Campaign and then waits for the execution time of the first scheduled run. As a run completes, the system schedules the next run and repeats this process until all runs are complete.
For Campaigns where the end date is not specified, the system generates the upcoming schedule for the first ten runs. It will add the next set of runs to the upcoming schedule when there are fewer than five runs remaining. To configure the number of runs the system generates at a time, click Settings in the Pega Express navigation bar, then click.
Once all scheduled runs of a Campaign are complete, the scheduled execution cycle is also considered to be complete.
The system listens for configured Events during the configured time frame. If an end time is configured for the window, the Campaign stops listening for the Event once the end time is reached. At this point, the event execution cycle of the Campaign is considered to be complete.
The system responds to Container requests during the configured time frame. If an end time is configured, the Container will no longer consider this Campaign once the end time is reached. At this point, the container execution cycle of the Campaign is considered to be complete.
Previous topic Skipping a Run Next topic Managing Concurrent Campaign Data Flow Runs