Rules and Status

A journey's rules do not decide whether it can be saved: an incomplete journey is saved anyway. They decide whether it is shown to the customer, and when in doubt the answer is no. A journey that fails any rule is not shown on any flow. The customer never sees a partial indicator: they see the screen as if the journey did not exist.

The four statuses

The journey's status panel and the journey list sum it up in one of four answers:

Status	Rules	Enabled	What the customer sees
Shown to the customer	All pass	Yes	The indicator
Ready, but turned off	All pass	No	Nothing. Turn the switch on and save
Still to finish	Some fail	No	Nothing. It costs no customer anything, but there is work left
It is on and the customer does not see it	Some fail	Yes	Nothing, while whoever set it up believes it works. Fix it or turn it off

In the list, the fourth status shows as Not shown, with the failing rules in parentheses.

While there are no steps, the panel does not talk about rules, because all of them would fail for the same trivial reason. It first shows what is missing (pick the entry, wait for the proposal) and then Proposal ready, with how many flows it reached, how many steps it proposes and how many flows it proposes to exclude.

The rules

Rule	What it requires	How to fix it
V1 · There are no steps yet	At least one step.	Use the proposal or add a step with the entry flow.
V2 · There is an empty step	Every step has at least one flow.	Assign a flow to it, or delete the step.
V3 · Step numbering is broken	Step numbers are unique and consecutive from 1.	Moving or deleting a step on the screen renumbers them on its own, so this only shows up on journeys created some other way.
V4 · A flow is in two steps at once	Each flow appears only once.	Assign it to the step where it belongs: it leaves the other one on its own.
V5 · A flow in the journey does not exist in the tenant	The entry flow and every flow in the steps exist.	It was deleted or an id went stale. Take it out of the step or point at a flow that exists.
V6 · Some flows are not assigned to a step	Every flow reached from the entry is in a step or excluded.	Assign each one to a step, or exclude it. They are listed under Assign them to a step.
V7 · The entry flow is not in step 1	The entry flow is in the first step.	Move it to step 1: it is where the customer comes in.

A flow that exists but is not reached from the entry does not break V5. That is a warning, not a rule (see Warnings).

Three more conditions are not shown as rules on the screen, and they also stop the journey from showing:

Two journeys with the same entry flow. Neither of them is shown. Both can be saved without an error, and the panel of each one can say Shown to the customer, so check the list: two rows with the same entry are this case.
The journey was never checked against the flows. A journey saved from the screen always has been. If you see this reason in a notice, open the journey and save it.
A mode that is neither Sequence nor Checklist. The screen does not let you choose another; it can only happen with a journey created some other way.

When the rules are checked

There are two separate checks, and it pays not to confuse them.

The screen checks the rules live while you edit, against the flows as they are now. V5 waits for the flow catalog to load and V6 waits for the proposal. While either is missing, the panel says Not checked here: the screen could not check it, but the system still applies the rule.

What the customer sees depends on the check stored the last time the journey was saved:

V1 to V4, V7 and the mode are checked again every time a customer opens the entry flow. They only depend on the journey.
V5 and V6 depend on the flows, and they are only checked when the journey is saved. The result is stored as a snapshot of how the flows were at that moment.

After changing the flows of a journey, save it again. Publishing, deleting or renaming a flow does not update that snapshot:

You delete a flow that is in a step: the journey keeps showing with the old map until you save it. On save, V5 fails and it stops showing until you fix it.
You add a Jump To towards a new flow: on save, that flow shows up unassigned and V6 fails. Put it in a step or exclude it.
You rename a flow: in Checklist mode the customer keeps seeing the item's old name until you save.

Until you save, the panel, which checks against the current flows, can say something different from what the customer sees.

Warnings

Warnings do not stop a journey from showing. They appear in the Warnings card and point out mismatches between what is reached from the entry and what the steps say:

Flows in a step that the entry never reaches. The customer would never pass through them, so that step would never be marked. It may be a missing Jump To, or a flow that does not belong in the step.
Exclusions for flows the entry no longer reaches. They are left over from an earlier version of the flows. They do no harm, but they are not needed.
The proposal's warnings: jumps to flows that do not exist, flows that jump to themselves, jumps back, and graphs over 200 flows (see Building a Journey).

Every flow named in a warning can be clicked and takes you to its preview.

When an enabled journey is not shown

If a journey is turned on and cannot be shown, because a rule fails, it was never checked against the flows, or another journey has the same entry, the system leaves a notice on the conversation:

Code: journey_not_served. The panel does not have a label for this code yet and shows it raw.
Level: warning.
Message: El recorrido configurado no se puede mostrar, which means the configured journey cannot be shown.
Reason: a summary of the failing rules.
Details: the journey id and each failing rule, with the flows involved.

It is written once each time the customer opens the flow, never per message. It is only written when the customer's browser already has a conversation with that flow, because that conversation is where it is recorded. A customer's first visit leaves no notice. A journey that is turned off leaves no notice at all.

Notices are visible in Chat and in Flow Notices, and the code is listed in Notice Codes.

Before turning it on

The panel says Ready, but turned off, with no rules left unchecked.
The list has no other journey with the same entry flow.
Every step has a stage name, not Paso N.
In Checklist mode, the flows of each step have a name written for the customer.
The excluded flows really are detours: review the ones excluded because of their name.
The link you share is the entry flow's link.
Turn on Enabled, save, and open the link in a new window to see the indicator the way the customer sees it.