Running a Journey Test again

Tookii · September 15, 2026 · 5 min read

A Journey Test used to be one-shot. If a run surfaced a bad frame, a missing task, or a technical error, the only way forward was to rebuild the whole flow from nothing. One early tester rebuilt theirs four times in one sitting.

There are now two ways to change a test and run it again, and between them they cover everything:

• Run again copies a finished run's flow into a fresh draft and opens it in the wizard with the same personas. Change a task or the goal, then run.
• Update from Figma pulls the prototype's current state onto a flow you are already holding, keeping every task you wrote.

Neither destroys anything. If you want to begin from nothing, that is what New test on the Tests page is for.

Doing it

1. Open a finished Journey Test report: click its card on the Tests list.
2. Press Run again, top right, next to New test.
3. You land on the flow canvas with the whole flow restored: every screen, its task, the connections between them, and the goal. The personas from the original run are already selected.
4. Change whatever you came to change: a task's wording, the order of two screens, a frame you want gone.
5. Press Run test.

Step 4 is optional. If the first run failed for a reason that had nothing to do with your flow, press Run test straight away.

What you get, and what you don't

The copy carries over: every screen and its stimulus, the tasks you wrote, the connections, the goal and its success criteria, and the cast of personas.

It does not carry over: the original run's results. Those belong to the run that produced them.

The original is never touched. Its report keeps describing the walk it actually recorded: same status, same flow, same findings. Run again always works on a copy, which is also why you cannot edit a finished test in place. A report that changed under you would stop being evidence of anything.

It does not start the run for you. You land with Run test armed and press it yourself. A run spends a test credit, and the usual reason for coming here is to change something first.

Where the copy lives

The moment you press Run again, the copy exists as a draft. It appears on your Tests list with a Draft badge, named after its first screen.

That means you can walk away from it. Close the tab, go look at something else, come back tomorrow: the draft is on the Tests list and clicking it puts you back on the same flow. Everything you type on the canvas is saved as you go.

Two things to know about coming back:

• Reopening from the Tests list asks you to pick personas again. The flow comes back whole; the cast doesn't travel in the card's link. Reopening from the browser's back button, or a URL you kept, keeps both.
• Pressing Run again twice makes two copies. Each is its own draft. Leaving one unused costs nothing. A draft never runs on its own.

Reading the save state

Next to the Run test button, the wizard says where your work stands:

Saving happens on its own about a second and a half after you stop making changes. There is no Save button and nothing to remember to press. But if you are about to close the tab, glance at this first: Saved is the only one of these that means your work is safe elsewhere.

Your Figma changed since the last run

Press Update from Figma, on the flow canvas. It goes back to the file you imported from and pulls its current state onto the flow you already have.

The split is: Figma owns the pictures, the screen names, and which screens exist. Tookii owns the tasks, the goal, and the layout. So a re-sync gives you freshly rendered frames and any renaming you did in Figma, and leaves every task you wrote exactly where it was.

• A screen you added in Figma joins the end of the flow, before the goal. It arrives with no task. That one's yours to write.
• A screen you deleted in Figma is removed, and the flow closes up over it: whatever pointed at it now points at what it pointed to.
• If you reordered or rewired screens by hand, that survives. Re-syncing does not put the imported order back.
• Notes and the goal are never touched.

It tells you what it did ("3 screens refreshed · 1 added. Your tasks and goal were kept.") so a sync that found nothing new doesn't look like a sync that failed.

It only works on a draft. A finished run's flow is frozen, so press Run again first and update the copy.

"This flow has no Figma link on record." Flows imported before the link was recorded have nothing to go back to. Import the file again on a fresh test, and re-sync will work from then on.

If something goes wrong

There is no "clear this flow" button. By design. To change the screens, use Update from Figma; to start from nothing, use New test. A destructive button on the canvas only ever cost people the tasks they had written.

"That test has no flow to run again." The original has no screens stored against it. Journey Tests from before flows were persisted can look like this. There is nothing to copy, so build the flow fresh with New test.

Run again does nothing / shows an error. The copy is a single write; if it fails, nothing is created and the original is untouched. Press it again.

The copy's screens are blank. The copy points at the same stored screen images as the original rather than duplicating them. If those images are gone, re-import the screens on the canvas.