Troubleshooting journeys - Amazon Pinpoint
Event based journey isn't triggered when using a PutEvents requestAll journey participants go through ‘No’ branch during ‘Yes/No’ split activity

Troubleshooting journeys

Verify that logging is turned on to assist in identifying the cause of failure. For more information on logging, see Monitoring and logging and Journey events.

Event based journey isn't triggered when using a PutEvents request

Issues and solutions

  • Verify that the configured Journey limits are not being exceeded:

    • Maximum daily messages per endpoint

    • Maximum number of messages an endpoint can receive from the journey

    • Maximum number of journey messages per second

    • Maximum entries per endpoint

  • Ensure that the active number of event triggered journeys does not exceed the provisioned threshold. For more information, see Quotas.

  • Verify that all components of the PutEvents API request are complete, including Event Component and Endpoint Component.

  • Verify that the specific journey is in the same application as the one in the PutEvent request.

  • Verify that the correct event is configured to activate your journey. You can confirm this configuration in the Journey entry condition.

  • Event-driven journeys are not conducive to Contact Center use cases because of the limited life span for dial operations is 3 minutes.

  • You can use the following example request to activate a journey using “TestEvent” as the entry condition.

    aws pinpoint put-events --application-id 7149cbb8XXXXXXXX --events-request file://PutEvents.json
file://PutEvents.json 
{
    "BatchItem": {
        "ExampleEndpointID": {
            "Endpoint": {
                "User": {
                    "UserId": "10107"
                }, 
                "ChannelType": "EMAIL",
                "Address": "johndoe@example.com"
                   
            },
            "Events": {
                "JourneyEvent": {
                    "EventType": "TestEvent",
                    "Timestamp": "2019-02-10T19:48:57+00:00"
                }
            }
        }
    }
}

All journey participants go through ‘No’ branch during ‘Yes/No’ split activity

Issues and solutions

  • This error can occur when no wait time is configured. Send events are evaluated immediately, which results in moving all participants to the 'No' branch.

    • To resolve this issue, verify that some wait time is configured after the condition evaluation.

  • Yes/No splits based on an event criterion and following custom AWS Lambda activities have an implicit wait time of 15 minutes to accrue and process the event outcomes.

  • Yes/No splits based on an event criterion and following channel activities (SMS, EMAIL, PNS) have a wait time of 1 hour to accrue and process the delivery event statuses for channel message deliveries.

  • Only standard events specific to channel delivery statuses are supported for Yes/No splits.