Journeys

Teach a check, then start watching ​

Every new check gets an attended first run. You watch what Journeys does, correct it when necessary, and approve a successful path before any scheduled run is allowed.

Run the Draft ​

Open a Draft check and choose Run. If the check requires variables, Journeys asks for values before the run. You can override a default for this attempt without changing the saved default.

The run page shows the browser and Activity as the agent works. A run you started yourself has controls to:

  • Pause before the next browser action.
  • Resume a paused run.
  • Send a short piece of guidance when the agent needs help.
  • Stop a queued or running attempt.

Guidance is recorded in Activity and marks the attempt as assisted. Scheduled, CI, dependency, and named-chain runs cannot be guided; their result must be unassisted to be useful monitoring evidence.

Do not leave a run paused indefinitely. Journeys eventually stops a run that uses its pause allowance, releases its browser slot, and keeps the evidence already collected.

Review the result ​

If the run fails, use its Activity, screenshot or recording, and diagnostics to understand where it went wrong. Choose Edit check when the definition needs work, or Retry when the instructions are sound and the path needs another attempt. A failed learning run cannot be watched.

After a pass, Journeys shows the memory learned from the run and asks whether it followed the path your product intends. Choose:

  • Retry when the result happened to pass by the wrong route.
  • Yes, start watching when the route and outcome are appropriate.

Approval is for the run and its path, not for each sentence in memory. Choosing Yes, start watching opens the schedule dialog; saving that dialog approves the check and arms it together.

How memory works ​

Memory is practical, fallible advice attached to one check. It is grouped into what worked, what to avoid next time, and orientation around the product. The next run receives all current lessons as advice, not as guaranteed truth.

Later passing scheduled runs can add or refine lessons without asking for approval again. A failing run does not rewrite memory. Editing the check also does not silently discard it.

Open the check's Memory section to remove one obsolete lesson or choose Clear all. Clearing all preserves run history, but the next run is cold and the check must learn successfully before it can continue unattended.

Retry instead of approving a lucky pass

A pass is not enough if the agent used a route that is unreliable, unsafe, or different from the customer path you mean to monitor. The attended run is your opportunity to make that distinction.