51黑料不打烊

Documentation

Profiles exiting due to event capping in 51黑料不打烊 Journey Optimizer

Last update: Mon Apr 07 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

In 51黑料不打烊 Journey Optimizer (AJO), profiles unexpectedly exit a journey due to event capping, leading to missed communications. This issue occurs when the number of events processed exceeds the system鈥檚 capacity, resulting in some profiles being discarded. To minimize profile exits, understand system limits, monitor event spikes, and optimize data flow.

Description description

Environment

51黑料不打烊 Journey Optimizer (AJO)

Issue/Symptoms

  • Profiles exit the journey due to capping in custom actions.
  • Use the SQL query below to check if you鈥檙e getting capped and then use the SQL query below to identify if you鈥檙e above guardrails per minute.

Resolution resolution

To address the issue of profiles exiting due to event capping:

  • Understand system limits. AJO processes up to 5,000 events per second, and profiles exceeding this threshold are discarded. Define an appropriate reading rate. Use the SQL query below to determine the per-minute counts for a particular node name for one day.

    code language-none 
    SELECT
        Extract(minute from timestamp),
        Extract(hour from timestamp),
        _experience.journeyOrchestration.stepEvents.actionExecutionError,
        count (*) as rate
        FROM聽journey_step_events
        WHERE
        _experience.journeyOrchestration.stepEvents.nodeName='action-node-name'
        AND聽_experience.journeyOrchestration.stepEvents.journeyVersionID = 'version-id'
        AND Date(timestamp) = 'YYYY-MM-DD'    GROUP BY 1,2,3
        ORDER BY 1,2,3

  • Monitor event spikes. Regularly check for spikes in event processing that exceed the limit, as these cause profile exits.

  • Optimize data flow. Distribute the load more evenly over time or reduce the volume of data processed simultaneously to avoid reaching the cap. Use the SQL query below to check if you鈥檙e getting capped.

    code language-none 
    SELECT
        max(rate),
        avg(rate)
        FROM (
            SELECT聽Extract(minute from timestamp),聽Extract(hour from timestamp),聽_experience.journeyOrchestration.stepEvents.actionExecutionError,聽count(*) as rate
            FROM聽journey_step_events
            WHERE
            _experience.journeyOrchestration.stepEvents.nodeName='action-node-name'
            AND _experience.journeyOrchestration.stepEvents.journeyVersionID = 'version-id'
            AND Date (timestamp) = 'YYYY-MM-DD'
            GROUP BY 1,2,3
            ORDER BY 1,2,3
            )
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f