# Creating a Jump for a Real Time Journey

With a real-time journey jump, you can send profiles to the destination journey stage based on their behaviors during the journey.

![](/assets/rtjump.233a8bbcfabdb8bb22301a61f1ce4b23c2edc34253a6f40f61d2fc33a01ce224.9e7171ae.png)

## Limitations

* You cannot jump to a previous stage in the current journey.
* Circulating jumps is not supported. For example, you can jump from Journey A to Journey B and then back to Journey A.
* A journey can support a maximum of 20 jumps.


## Create a Jump

When you add a jump event to your journey, the jump becomes the final condition because you cannot follow a jump with any other event. You can add multiple jumps within the same journey stage by adding jumps to different decision point paths and multiple jump events to the different journey stages.

1. Open TD Console.
2. Navigate to Audience Studio.
3. Open an existing journey or [create a journey](/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey).
4. Drag the jump event to your journey workflow.
The following jump destinations are supported:


* A different stage in the same journey
* A stage in a different journey [draft or launched](/products/customer-data-platform/journey-orchestration/batch/understanding-journey-statuses)
* When the journey meets its goal
* After meeting the exit criteria


* If you add a jump to a stage in a different journey, you must have full access permission for the different journey. If you don't have full access permission, you cannot select the journey.
* You cannot add or remove a jump after launching a journey.
* The jump profile doesn't have to fulfill the entry criteria of the destination journey stage.


1. Name your jump event.
2. Select the profiles that will move to the designated jump destination:


* (Optional) Filter for draft or launched journeys.
* (Required) Select the stage in the same journey or a different journey.


1. Select **Save jump**.


## Examples

* [Journey Type Filter](/products/customer-data-platform/journey-orchestration/realtime/creating-a-jump-for-a-real-time-journey#journey-type-filter)
* [Same Journey Jump](/products/customer-data-platform/journey-orchestration/realtime/creating-a-jump-for-a-real-time-journey#same-journey-jump)
* [Different Journey Jump](/products/customer-data-platform/journey-orchestration/realtime/creating-a-jump-for-a-real-time-journey#different-journey-jump)
* [Goal Journey Jump](/products/customer-data-platform/journey-orchestration/realtime/creating-a-jump-for-a-real-time-journey#goal-journey-jump)
* [Exit Criteria Jump](/products/customer-data-platform/journey-orchestration/realtime/creating-a-jump-for-a-real-time-journey#exit-criteria-jump)


### Journey Type Filter

![](/assets/image2023-3-22_16-1-19.fd3934962e78746aa39b2a211f70b4dda38ef52a93d08c6349b97cadc1ee8fe4.9e7171ae.png)

### Same Journey Jump

![](/assets/image2023-3-24_13-5-26.2cada61e9b0b92b54c8e9cf110b382f6d8dc713f2a6f22310372fcd66f321d99.9e7171ae.png)

### Different Journey Jump

![](/assets/image2023-3-24_14-28-19.b296df412720bd9c686d2e49d5afb1fc46a3f17d5a6cb1c773c741160586320b.9e7171ae.png)

### Goal Journey Jump

![](/assets/image2023-3-28_14-31-7.6ed1f09802714ac2b14e3d8f860b83c9a932c1094c06013ed8c75deeb62004c0.9e7171ae.png)

### Exit Criteria Jump

You can include a jump for custom exit criteria as well as a stale profile.

![](/assets/image2023-3-28_14-46-4.a1130920cf77801040299bb343a9fcc8921892f2fed1c40554adcec9c1daaf91.9e7171ae.png)

# Understand the Move Profiles File Path

In the following example, the file path first lists the stage name, journey, and folder names.

![](/assets/image2023-3-24_14-31-53.0d4f4a18f7913d120920460086f9d8ac0ecab1d2ecc0a32d6de3ab36222b89cd.9e7171ae.png)

# Jump Edge Cases

The following edge cases describe behaviors you might not expect or anticipate when creating a jump.

## Duplicated Profiles in Target Journey

There might be an instance where the same profile exists in the original and targeted journeys for the jump.

![](/assets/image2023-3-27_10-51-32.246bbd5001b59bb19b6b94d9c76a8079622e32d274ad49ee551faeafd73d25b0.9e7171ae.png)

Profile A meets the *qual_cust* journey's *Awareness* stage criteria in the previous example. The jump's target is to the journey *onboard* , stage *Enroll*. However, Profile A is already in *SMS* of the target journey. The state of Profile A in the *onboard* journey is not reset; because the profile is already in SMS, the profiles remain in SMS.

Jump from Multiple Journeys

In the following example, Profile A qualifies for a jump to the journey stage *In cart* in journey *purchase*. Profile A also qualifies for a jump to the journey stage. *Confirm* in journey *purchase*.

![](/assets/image2023-3-27_15-39-43.eea4641f3bc4d750fa69ecda38e9d45b579e6a10c7d833e0b5c31fb97f95c2a9.9e7171ae.png)

Treasure Data Journey Orchestration rules dictate that if multiple destinations are in the same journey for a single profile, the profile should jump to the "lowest" stage.

See also [Journey FAQs](/products/customer-data-platform/journey-orchestration/batch/journey-faqs).