Cancelling a running generation

While a generation is running (see generating your first module), you can stop it before it finishes. This page covers how, and what to expect afterward.

Stopping a run

1. Click Stop. The button sits next to the progress bar at the bottom of the Generating screen, and is available through every phase — Discovery, Implementation, Validation, Browser Testing — until the run completes.

2. Confirm. Stop swaps in place for two buttons: Continue generating, which cancels the click and leaves the run untouched, and Stop generation, which confirms it. Nothing happens until you choose the second one.

3. The run ends. Confirming stops the generation within moments. You’ll see a “Generation stopped” notice and land back on the requirements screen, not an error page.

What stopping does to the run

Stopping kills the generation immediately and marks it as failed in your generation history — there’s no partial or paused state to come back to. If you check the Modules Library or your generation history, a stopped run shows there the same way any other failed run does.

Note

A stopped run still counts as one of today’s generation attempts, even though it never finished — the daily cap (see generating your first module) is based on how many runs you started, not how many completed.

Starting another generation

You’re normally free to start a new generation right away — OdoMate only enforces one generation at a time, and stopping ends the one you had.

Note

When you confirm stop, the generation stops immediately — there’s no background finishing process. You’re free to start a new generation right away without waiting.

If you still need the module

Stopping doesn’t save any progress to resume later. If you still need the module, start over from generating your first module with the same or an adjusted requirement.