Journeys

Choose or write a check ​

A check tells Journeys where to begin, what outcome to verify, and any values it may use. Start with a catalog check when it fits; write a custom check when the behavior is particular to your product.

Catalog checks ​

Catalog checks are maintained by Journeys. Their name, start path, instructions, variable definitions, and outputs are locked so updates can remain consistent. You can supply variable values, choose the schedule, and teach the check on your own site.

If you need to change the definition, choose Duplicate & edit. Journeys opens an editable custom copy. The copy is not stored until you choose Save, and it begins as a new Draft with its own memory.

Deleting a catalog check removes it from the site. You can add a fresh copy from the catalog later, but its former values and learned memory do not come back.

Custom checks ​

Choose Write your own check, or open Add check → Write your own check on an existing site. A definition has:

  • Name — a short description of the behavior being watched.
  • Start URL — the first page Journeys opens. It must stay within the site.
  • Instructions — the outcome and boundaries for the browser agent.
  • Variables — reusable values, including values that should be secret.
  • Outputs — values this check may publish to a following check.
  • Memory — learned advice from successful runs, once any exists.

Choose Save to store the definition. Saving does not run or schedule the check. Choose Run for an attended attempt; the editor can run an unsaved definition when it has a start URL and instructions, but that ad-hoc run will not appear in the site's History.

Write instructions that can be judged ​

Describe the result a person should be able to observe, and identify important limits. For example:

Search for . Open the matching product and confirm its product page shows a price. Do not add it to the cart.

Prefer an observable finish over a list of pixel-level clicks. Mention actions that must not be taken, especially submits, purchases, messages, deletions, and changes to account data. Use a variable for a value that changes or must be protected.

A check is browser automation against your real product. Use a test account and test data when the flow can write data, incur a charge, notify a person, or use a paid seat.

Change or remove a check ​

Open a check to edit its definition. Existing memory is not automatically cleared when the instructions change, so inspect it and remove advice that no longer applies.

For a watched custom check, Stop watching removes its schedule and any dependency while keeping the definition, variables, secrets, and memory. Delete the custom check from its editor only when you also want to remove that saved definition and its memory.

A check cannot be removed while other checks are set to run after it. Journeys names those followers; change them first, then try again.