Editing & Re-running a Test

Once a run reaches completed or failed status, its detail page shows two ways to run it again: Re-run (runs it again exactly as-is) and Edit & Re-run (lets you fix or change a step first). A draft run (one that hasn't executed yet) shows a similar Edit steps link next to its Run this test button, for the same reason: to fix something before it ever spends a credit.

Re-run (exact repeat)

Clicking Re-run:

1. Clones the run (same target URL, same viewport, same Chaos Mode setting, and an exact copy of every step) into a brand-new run row, with its own fresh ID, its own fresh public share slug, and its own fresh CI trigger token.
2. Immediately triggers that new run, deducting credits from your balance the same way clicking Run this test on a draft would (1 credit normally, 3 with Chaos Mode).
3. Redirects you to the new run's detail page, where it starts at queued status just like any other newly-triggered run.

This is the fastest way to check "does this still work" after making a change to your app, without touching the scenario itself at all.

Edit & Re-run (fix something first)

If the run failed because a step was misconfigured (a wrong description, the wrong target URL, a step in the wrong order) rather than because your app actually broke, re-running it verbatim just spends another credit failing the same way. Edit & Re-run (on a completed/failed run) and Edit steps (on a draft) both take you to the same place instead: the familiar New Playtest form (see Creating a Playtest Run), pre-filled with that run's target URL, viewport, Chaos Mode setting, run label, and every step exactly as they were.

From there:

1. Change whatever needs changing: fix a step's description, add or remove steps, switch the target URL, flip Chaos Mode, or even pick a different starting template entirely (picking a template replaces the pre-filled steps, the same as it would on a blank form).
2. Click Confirm & Create Run, exactly like creating any other run.

Two things distinguish this from Re-run:

• Nothing is spent yet. Editing and submitting creates a fresh draft, the same as /runs/new normally would. A credit is only deducted once you click Run this test on that new draft, so you can review your changes once more (or walk away entirely) before committing to it.
• It never modifies the run you started from. Whether you began from a draft or a completed/failed run, editing always creates an independent new run row. The original is completely untouched. This is the same "always clone, never mutate" approach Re-run and the CI/CD trigger both use.

One detail worth knowing: the "Starting point" template dropdown on the edit form still works, but picking a template replaces your pre-filled steps with that template's defaults, the same way it would when writing a run from scratch. If you only want to tweak one step, leave that dropdown alone and edit the step rows directly.

Choosing between them

	Re-run	Edit & Re-run / Edit steps
Available from	completed/failed	draft, completed, or failed
Steps	Exact copy, unchanged	Pre-filled and editable
Credit spent	Immediately	Only once you click Run this test again
Use when	The scenario was right; you just want to check again	The scenario itself needs fixing or changing

Both share the same underlying idea as the CI/CD trigger endpoint: create a fresh, independent run from an existing one's configuration rather than ever mutating a run in place.