Back to Knowledge Base

Websites & Test Flows

Website detail & test flows

A single website hub with preview, status breakdown, and the list of its test flows.

The website detail page is the hub for a single monitored website. It shows an overview of the site and lists all test flows belonging to it.

Key functions

Header actions

  • Back to overview — return to the websites list.
  • Domain link — open the live site in a new tab.
  • Copy — copy the domain URL to the clipboard.
  • Settings — open website settings (name, type, client, cookie selectors).
  • Add test flow — start the add-website wizard for a new flow on this site.
  • Delete — remove the website and all its test flows and runs (confirmation required).

Website preview

  • A card shows a screenshot preview of the site.
  • Retake screenshot captures a fresh preview (may take a moment to appear).

Website status

  • A donut chart summarizes all flows on this website:
    • Passed
    • Failed
    • Error
    • Pending
  • The center shows the total number of test flows; a legend lists counts per status.

Test flows table

  • Lists every test flow for this website.
  • Each row shows name, type, and status (latest run result; paused flows also show a Paused badge).
  • Click a row to open the test flow detail page (schedule and run history).
  • Per-row Settings opens that flow’s configuration.

Bulk actions

  • Select multiple enables checkboxes on the table.
  • Select one or more flows, then:
    • Pause — stop scheduled runs for selected flows.
    • Activate — resume scheduled runs.
    • Delete — remove selected flows and their runs (confirmation required).
    • Run manually — trigger an immediate test for each selected flow.
  • Done exits selection mode.

Empty state

  • When no test flows exist, the table prompts you to Add test flow.

Plan availability

  • Run manually (single or batch) is disabled when the trial has ended — the account is read-only and new runs cannot be started.

Tips

  • Use the status donut to spot failing or pending flows at a glance before opening individual flows.
  • Pause flows you are actively editing so scheduled runs do not interfere with your changes.