Execution of journeys fail while executing multiple journeys in parallel

About Article:

This article will cover how you can resolve the following issue:

1. When using an execution planner, Journey execution fails, but manual execution is successful.

Description:

The execution planner is failing when there are a lot of Journeys, but manual executions are still successful.

Solution:

It is primarily due to application slowness. The app may struggle with handling multiple parallel executions. Consider the following points:

Check below things:

Are users encountering network/loading errors or errors in element identification? If they are facing network/loading errors, the issue likely lies with the application’s bandwidth. For both scenarios, try the following workarounds:

a) Enable wait for network traffic from the goal settings (under interaction tab)

b) Add sufficient “wait for” steps after new page loads (Ex: Wait 20 seconds for "Username")

c) From goal settings - Try reducing the number of journeys getting executed in parallel to 50% of the current parallel executions, if the problem persists try reducing the setting the parallelism to a low value like 3 or 4