Skip to content

Manage journeys

This guide covers the day-to-day tasks for synthetic journeys after they are recorded.

  • The admin role for every task that changes something. Members and viewers can read run history and journey incidents only.
  • Journeys in the sidebar. It is included from the Max plan, and a platform operator switches it on for the workspace.
  • Access to the Auth0 dashboard for the tasks that change the probe user.

Two menus are used in this guide:

  • The tenant menu is on the tenant card. Its label is “More options for (tenant)”.
  • The row menu is on a journey row. Its label is “More actions for (journey)”.

To record a new journey, see Record a journey. For what each status and label means, see Synthetic journeys.

Use this when the client changes their sign-in page, when a check is wrong, or to finish a journey left under Awaiting first pass.

  1. Open Journeys.
  2. If the journey is failing, click its row and open the failed run. Note the step marked Stopped here and choose View screenshot.
  3. Open the row menu and choose Edit steps. The page Edit steps: (name) opens, with the badges “Tenant: (name)”, the type, and Running or Off.
  4. Change the steps. You can delete or move a step, supply a value, Add a check, Add Enter key press, Add MFA step, or change Allowed hosts. The editor is the same as in the record wizard. See the step editor.
  5. Choose Save changes.
  6. Choose Run a test and wait for The test run passed.
  7. Choose Start running.

What saving does:

You changed Result
A step, a value or an allowed host The warning Saving turns this journey off shows before you save. After saving you see “Journey saved. It is off until a test run passes.” The journey moves to Awaiting first pass until a test passes and you choose Start running.
Only the schedule or Run from You see “Journey saved.” The journey stays as it was.

If nothing is unsaved, Go to the test takes you straight to the test step. Use this to finish a journey under Awaiting first pass: choose Edit steps, Go to the test, Run a test, then Start running.

You cannot rename a journey, change its type or change its start URL. If the page changed a lot, delete the journey and record it again.

You should see: the journey back under Running, and then Passing.

How often it runs

  1. On the journey row, open the schedule select.
  2. Choose the new interval. It saves at once, and you see “Schedule updated”.

Sign-up (Registration) journeys offer Hourly, Daily and Weekly only. Other types can run as often as every 5 minutes.

Where it runs from

  1. Open the row menu and choose Edit steps.
  2. Under Journey settings, Run from, tick EU, US or both. At least one must stay ticked.
  3. Choose Save changes. The journey stays on, because no step changed.

The Edit steps page is the only place to change the regions after the journey is created.

  1. Open the row menu.
  2. Choose Pause. You see “Journey paused”, and the journey moves to Paused.
  3. To start it again, open the row menu and choose Resume. You see “Journey resumed”.

Pause and Resume appear only after the journey has passed once. A journey under Awaiting first pass has neither.

A paused journey has no lane in the Live journey map and is not counted in Failing or Couldn’t finish.

  1. On the journey row, choose Run now. You see “Run queued”.
  2. The row shows Queued, then Running now, then the result. The card refreshes every 5 seconds while a run is in progress.

Run now is disabled while a run is queued or running. There is no other waiting time between runs.

  1. Open the row menu and choose Delete.
  2. The confirmation reads “Delete (name)?” with “It stops running immediately. Past results are kept, but it would have to be recorded again.”
  3. Choose Delete journey. You see “Journey deleted”.

An open journey incident for the journey is closed without a message.

Use this when the probe password is lost, when the probe user was deleted in Auth0, or when runs show Probe credentials rejected.

  1. Open Journeys.
  2. Open the tenant menu and choose Reissue probe credentials.
  3. The dialog New probe credentials opens, with the warning “Copy the password now. It cannot be shown again.” Choose Copy beside the password. The email address is the same as before.
  4. In the Auth0 dashboard, set that password on the probe user. If the user was deleted, create it again with the same email address and connection.
  5. Back in Identiguard, choose Done.
  6. On a journey, choose Run now.

You should see: the journey shows Passing.

Use this when runs show an MFA problem such as No stored secret for the multi-factor challenge, or when the probe user was enrolled with a device Identiguard does not hold.

The reset has two halves, and you need both. Identiguard cannot reset MFA in Auth0 for you.

  1. In the Auth0 dashboard, reset MFA for the probe user.
  2. In Journeys, open the tenant menu and choose Reset MFA.
  3. The confirmation reads “Reset MFA for the probe on (tenant)?”. Choose Reset MFA.
  4. You see “MFA reset. Now reset MFA for the probe user in the Auth0 dashboard.” If you have not done step 1 yet, do it now.
  5. On a journey with an MFA step, choose Run now. The probe is expected to enrol its own factor on that run. This is not confirmed for every MFA method. If the run still stops at MFA, record the journey again and enrol with Fill code or the recorder’s passkey.

The probe password is not changed.

You should see: the journey shows Passing, and the tenant card shows the factor badge again after “MFA”.

  1. Open the tenant menu and choose Remove journey monitoring.
  2. The confirmation reads “Remove journey monitoring from (tenant)?” with “Recorded journeys are deleted too. The Auth0 accounts are not; you will be told which to remove.”
  3. Choose Remove monitoring.
  4. Note the addresses in the message “Monitoring removed. Delete these in Auth0: (addresses)”. The list holds the probe address and the addresses that earlier sign-up runs used. If there is nothing to delete, the message reads “Monitoring removed”.
  5. In the Auth0 dashboard, delete those users.

You should see: the tenant moves back to Not set up yet at the bottom of the Journeys page. Open journey incidents for the tenant are closed without a message.

Any member or viewer can do this.

  1. Start at the banner at the top of Journeys. For “N journeys failing: (journey) on (tenant)”, choose the linked journey name to jump to its row.
  2. On the row, read the status. Red with Failing or a failure label is a real failure. Grey or amber with Couldn’t finish: (reason) is a problem with the monitoring script: “Our script, not your outage”.
  3. Note Down since (date and time) if an outage is open, or Slow if a slowdown is open.
  4. Hover the bars of the history strip to see the region, the duration and the reason for each run. Choose View run to open that run.
  5. Or click the row to open the recent runs: the last 50, 5 to a page. Failed runs are open by default.
  6. In a failed run, read the step list. Stopped here marks the step where the run ended. Choose View screenshot to see the page the probe was on.
  7. Open Incidents (N) at the bottom of the tenant card. For an outage, read the downtime (“at least N min”), the number of failed checks and the reason. For a slowdown, read how long it was slow and the peak against the usual time.

Journey incidents cover the last 30 days. They are separate from the Incidents page. For the rules that open and close them, see Journey incidents.

What you see Why What to do
No Run now, schedule select or row menu You are not an admin Ask a workspace admin
No Pause or Resume in the row menu The journey has never passed Run a test that passes first. See Edit steps and re-verify.
A journey under Awaiting first pass passed with Run now but is not running A pass does not start the schedule Look for the journey under Paused and choose Resume. If it is still under Awaiting first pass, use Edit steps, Go to the test, Run a test, Start running.
“The change did not save” A pause, resume, schedule change, run or delete failed, for example a schedule that the journey type does not allow Try again and read the detail in the message
“This journey already has a run in flight.” A run is already queued or running Wait for it to finish
“Journey monitoring is switched off for this tenant.” Monitoring for the tenant is off The documentation team could not confirm how to switch it on again from this page. Escalate to the product team.
“Journey monitoring was disabled automatically after repeated failures. Resolve that first.” 5 consecutive Probe credentials rejected results Reissue probe credentials and set the password in Auth0. If runs are still refused, escalate to the product team.
“This tenant is backing off after recent failures. Try again shortly.” Identiguard is waiting after repeated failures Wait, then try again
“Saving turns this journey off” You changed a step, a value or a host This is expected. Save, Run a test, then Start running.
“Leave without saving your changes?” with “The journey stays as it was saved.” You are leaving Edit steps with unsaved changes Stay and save, or leave to discard the changes
“Could not switch the journey on” The journey has not passed a test Run a test that passes first
“Could not reissue the credentials”, “Could not reset MFA” or “Could not remove monitoring” A server error Try again
“The journey settings changed while this was being removed. Try again.” Someone changed the journeys at the same moment Try again
“Could not load the runs” with “The request did not come back.” The run history did not load Choose Retry
“No screenshot was taken for this step.” No screenshot was captured for that failure Use the step list

For the meaning of each run result, see Troubleshooting in Synthetic journeys.