Journeys

Troubleshoot a check ​

Start with the state on the site page, then open the newest relevant run. The Activity, browser recording, result text, and diagnostics usually distinguish a product failure from a run that could not make a fair check.

The check stays Draft ​

Saving or adding a check does not start it. Open it and choose Start learning. A failing run offers Retry or Edit, but cannot be watched. After a pass, review the route and choose Yes, start watching, then save a schedule.

If a passing learning run already exists, Review the run opens it instead of spending credits on another attempt.

A scheduled check does not run ​

Look for one of these states:

  • Paused — resume it; changing its schedule alone does not resume it.
  • Follows another check — it runs from its parent's schedule, and may be Not run if the parent failed or did not publish its required values.
  • Out of credits — buy a credit pack, wait for plan credits, or restore your own key. Checks and schedules are preserved.
  • Key not working — replace or remove the key in Settings.
  • Needs account — supply the required tested-app credential or secret value.
  • Uncaptured saved session — run its selected login check successfully to fill it, or choose a captured session in the check editor.
  • Draft — finish the attended learning and approval step.

A run can also remain queued while all of the account's browser slots are in use. It starts when a slot is released. Stopping it before its first step spends no credits.

The result says Could not check ​

Open the run and read its stated failure reason. Common causes include an expired saved session, an internal browser or agent error, and a navigation refusal. These do not count as Down or enter the uptime denominator.

Journeys allows only HTTP and HTTPS navigation within the site's fence. Private addresses, denied hosts, unsupported schemes, and a redirect outside the allowed site can be blocked. Activity names the refusal. Change the tested flow to stay within the site, or contact support when a legitimate product flow now uses a different required domain.

A check took the wrong route ​

During a manual run, pause and send a concise correction. After the run, make the durable fix in its instructions, variables, start URL, or memory. Do not approve a lucky pass that reached the outcome through an unsafe or irrelevant route.

Editing a check does not clear old memory. Remove a stale lesson individually; use Clear all only when the next run should relearn cold.

A following check says Not run ​

Open the parent run first. It either failed, published nothing, or omitted a required output. Confirm the parent declares the output, its description tells the agent what to find, and the follower expects the same name. Secret status does not change the name.

Running the follower manually is diagnostic and does not repair the missed scheduled sample. The next scheduled parent firing will try the line again.

No email arrived ​

Check the site's notification mode and recipient list. Failure-only mode skips passes, person-stopped runs, and skipped followers. Ad-hoc runs never mail. The recipient may also have unsubscribed; the dialog marks this and offers Re-enable. A service-level “email is not configured” banner means delivery is unavailable even though the preference is saved.

Use the newest sign-in message. A Journeys login link expires after 15 minutes and works once. Request another rather than reusing an old tab or forwarded link.

A secret appears empty while editing ​

That is intentional: Journeys never reads a stored secret back into the browser. An indicator says it is set. Leave the field blank to keep it, type a value to replace it, or use the explicit clear action to remove it.