Mass Listeners | Pricefx Knowledge Base

Mass Listeners enable high-volume event processing by listening for specific event types and triggering predefined actions. They are designed to process large volumes of events and support batching.

Difference Between Event Workflows and Mass Listeners

The main difference between Event Workflows and Mass Listeners is in their processing approach and purpose – see Workflows | Difference Between Event Workflows and Mass Listeners.

Mass Listeners Table

The table shows a list of existing Mass Listeners and their basic details. From this screen, you can create a new Mass Listener, or download the table in the CSV format (via the Export CSV button). In the row menu (the three-dots menu) you have the options to edit, show run history (log) or delete the listener.

Fields When Creating a New Mass Listener

Column	Description
Status (toggle)	Indicates whether the mass listener is currently Active and processing events, or Inactive. You can toggle the status by switching the button on or off.
Name	Displays the name of each listener. You can search for listeners by entering text in the search box above the column.
Description	Optional field to add context or notes about what this listener is for.
Event Source Type	Shows where the event originates. Possible options: PARTITION, or INTEGRATION.
Event Source	Specifies the exact source of the event. You cannot create a Mass Listener when a listener with the same source is already enabled.
Event Type	Select the type of event being processed. Available event types: Supported Event Types in PlatformManager \| Mass Listener Event Types.
Batch events before triggering an action	When enabled (default), the listener captures multiple occurrences of the event before executing the action. The action is triggered either 1 minute after the first event or after 500 events, whichever comes first. Batching reduces system load and improves efficiency for high-volume events. Disabling batching significantly slows down event processing.
Action Type	Specifies the type of action that will be triggered when an event is received.
Action ID	Specific action that will be triggered when an event is received. E.g. If Route is selected in the Action Type field, in Action ID select a route from the target IM instance. If Logic is selected in the Action Type field, in Action ID you can find a logic from the target partition to run.
Set fallback action (Checkbox)	Enables the fallback configuration section.
Number of attempts	Sets how many times to retry the primary action before triggering the fallback (default: 1).
Fallback Timeout	Sets a wait time (in minutes) between retries of the primary action. If no response is received, the fallback action is triggered.
Fallback Action	Skip the main action with no alternative: Ignores the failed main action and does not run anything else. Trigger alternative action: Executes a defined fallback action instead. Select the Action Type and Action ID of the action you want to be triggered.

Setting multiple fallback attempts and a long timeout may slow down the processing of all events for your account. This will also affect the processing of your other Mass Listeners and Event Workflows.