Journey cannot continue

When a Journey is played in the Newired Editor, the "Journey Cannot Continue" warning appears if the Journey is interrupted before it can be completed.

This can happen for several reasons, including connection issues, synchronization problems, or difficulties detecting the target element associated with a Journey Step.

This article explains the most common causes and how to resolve them.

Common causes and solutions

1. Connection to the Newired Server is unavailable

The Newired Editor may have lost its connection to the Newired Server.

How to resolve it:

• Check that your internet connection is working properly.

• Verify that the Newired Server is accessible by opening your Newired Portal in a browser.

• Once the connection is restored, try playing the Journey again.

2. The Editor and Server data are out of sync

The data in the Newired Editor may not be synchronized with the latest information stored on the server.

How to resolve it:

1. Click the Refresh button in the upper-left corner or select Reload Site in the Newired Editor menu.

2. Wait for the Editor to refresh.

3. Play the Journey again to check whether the issue has been resolved.

3. The Journey Step cannot detect its target element

This is the most common reason why a Journey stops unexpectedly.

Each Journey Callout Step is associated with a specific element on the target application. If the Editor cannot locate or correctly identify that element, the Journey may be unable to proceed.

How to troubleshoot it:

1. Identify the Step where the Journey stopped.

2. Open the Step for editing by clicking its Edit button.

3. Review the possible causes described below and apply the appropriate solution.

Troubleshooting target element detection

1. The target element is no longer available on the page

The element originally associated with the Step may have been removed, relocated, or replaced following changes to the target application.

Solution: Reassign the Step to the correct element currently available on the page.

2. The target element takes longer to load

Some pages or interface elements require additional time to load. If the Journey attempts to locate the target element before it becomes available, the Step may fail.

Solution: Increase the Extra wait time in the Step parameters to give the target element more time to appear before the Journey attempts to detect it.

3. The Step Identikit contains dynamic IDs or classes

Some applications generate element IDs or classes dynamically. Because these values can change between page loads or sessions, they may prevent Newired from consistently identifying the correct element.

Solution: Review the Step's Identikit and disable attributes containing dynamically generated values.

You can also configure these settings at the Site level in the Newired Portal, allowing them to be applied automatically to all Steps associated with that Site instead of configuring each Step individually.

4. Another element is detected instead of the intended target

In some cases, multiple elements on the page may share similar attributes. As a result, Newired may identify a different element instead of the intended target.

Solution: Open the Step's Selector Precision dialog and adjust the enabled or disabled attributes to make the element identification more precise.

This helps Newired distinguish the intended target from other similar elements on the page.

For detailed instructions, see: Fine-tuning the Step Element Detection.

Behavior in the Editor vs. the end-user environment

Note: The "Journey Cannot Continue" warning dialog is displayed only in the Newired Editor to help content creators identify and troubleshoot issues.

For this reason, we recommend testing your Journeys in the Newired Editor and resolving any element detection issues before publishing them.