Scheduled runs

A recorded flow is only worth as much as how often it runs. Recording a signup once and never running it again tells you the flow worked on a Tuesday — it doesn't tell you it still works today.

Put a suite on a clock

Attach a cron expression and a notify address to any suite. Test Chain replays it on that schedule — every fifteen minutes, hourly, nightly, whatever the flow warrants — from the same clean slate a manual replay uses.

*/15 * * * *   → runs every 15 minutes

Because each run is fully isolated (fresh cookie jar, namespaced storage, unique {{testEmail}}), scheduled runs don't accumulate state or trip over each other.

When something breaks

A failing step doesn't just flip a run red. The alert email tells you what you actually need:

• The exact step that failed — "Step 5 · Assert 'Order confirmed'" — not just "suite failed."
• A screenshot of the page at the moment of failure, so you can see the stuck spinner or the missing button without reproducing it.
• A link back to the run, where you can replay the exact recorded steps to confirm the fix.

This is the difference between finding out from a monitor and finding out from a customer. The flow that mattered enough to record is the one worth watching on a schedule.