Record and check
Changing a journey
Apps change. When a check fails because the app moved on rather than broke, the check is what needs changing, and BitAssure lets you change it without recording the journey again.
The Checks tab
A journey's Checks tab lists its scenarios in order, each with its steps and its checks between them. Beside each scenario:
- Fix this appears beside a check that failed in the last run. It opens that check so you can point it at the right element or correct what it expects.
- Change opens a check that passed, or has not run yet, for the same edits.
- Edit opens the recorder at that scenario, to re-record its steps or add checks.
Pointing a check at the right element
When a developer renames or moves something, a check can end up pointing at nothing. Point it at the right element lets you choose the element again. The check keeps its wording and its history, and so does every other check on that element.
Changing what a check expects
Open the check and change its value, for example when a price changed on purpose. Where the check sits in the walk is not changed here, because "Confirm is enabled" before typing and after typing are two different claims. To move a check, edit the scenario in the recorder.
Screens after a failed step
If the last run stopped at a step it could not do, the screens after it never ran. They are shown as locked, with the reason, because there is nothing known about them to fix. Fix the scenario where the run stopped, run the journey again, and the rest opens up.
Editing a scenario in the recorder
Press Edit beside a scenario. The recorder walks you to it and opens it as a draft:
- saving updates that scenario in place, keeping its checks and its run history
- the scenarios after it are kept and carry on from your new version
- ending without saving leaves it as it was
Archiving and deleting
From the journey's ⋯ menu:
- Archive this journey puts it away. It stops running, leaves the journey lists and the dashboard, and its schedules record why they stopped. Its runs and reports stay readable, and it can be restored.
- Delete permanently removes the journey, its scenarios, its checks and every run of it with its reports. This cannot be undone. Credits already spent are not affected.
If a platform's address changes, for example from staging to production, change it with Change address on the platform. Recorded steps that start with the old address move to the new one, and BitAssure tells you how many it moved.
This page as Markdown, for AI assistants: /docs/changing-a-journey.md. Every page at once: /llms-full.txt.