Handles requests to manually run a segment from the Segment rule form. If there are many manual requests for larger segments, then having this agent running on multiple nodes speeds up segment runtime.

Queue items for this agent are instances of the System-Queue-DeferredSegments class.

Manages the scheduled run of segments, which is configured in the Options and Schedule tab of the Segment rule form. If there are recurring runs, the agent auto-manages its own queue items. There should be only one queue item per segment at any given point in time.

Queue items for this agent are instances of the System-Queue-ScheduledTask class with the Agent Name set to PegaMKT-Engine:SegmentSchedule.

Initiates a campaign run at runtime. The agent creates the necessary infrastructure, such as batch classes and tables, and executes the strategy based on the segment input population that is configured. If configured on the campaign, it also triggers the refresh/rerun of the segment before starting a strategy. In a non-partitioned environment, this agent applies volume constraints.

Queue items for this agent are instances of the System-Queue-ProgramRun class.

Handles the processing of received real-time events. The agent reads the list of received events from a staging table, processes them, and then removes them from the table.

Processing an event involves:

• Checking the validity of the inbound event data for each of the associated campaigns
• Checking the validity of the customer (if configured)
• Assembling the appropriate context
• Executing the strategy associated with the campaign
• Executing offers that the strategy outputs

Executes the actions for the selected list of customers in a Field Marketing campaign.

Triggers an action flow for the WaitExpired paths in an action flow. Every campaign run creates one or more (if partitioned) of these queue items to periodically scan the batch table for records whose wait duration has expired. If any such actions are found, this agent resumes their processing along the WaitExpired path.

Queue items for this agent are instances of the System-Queue-WaitFlow class.

When actions are initiated in a non-batch scenario (such as Inbound), the records are stored in the MKT_DATA_OFFER table in the data schema. This agent scans through such actions to find any that have expired and resumes their processing along the WaitExpired path.

Queue items for this agent are instances of the System-Queue-GenericWaitFlow class.

For example, if the name of DB template was OutboundDailyNBA, then the job scheduler will be created, in the configured artifacts ruleset, with the name: OutboundDailyNBA__DB.

For more information, see Optional: Enabling the FinalizeFileDBTemplate queue processor.

Audience sync creates distributed map entry to avoid the rate-limiting error from other nodes.

In 8.5 distributed map entries persisted in Redis DB, even the full cluster restart will not clear these entries.

This job scheduler runs daily to identify the entries created by a failed node and removes them from the distributed map.

• The ProcessProgramRun agent has completed the processing for all of its actions. The status of all actions must be Completed
• The timeframe to purge a work object has lapsed. The timeframe is specified as a number of days. You can view this setting in the Pega Customer Decision Hub portal on the Application settings landing page, in the Delete campaign data older than field. For more information, see Application configuration.