Scheduled runs
A schedule (a “monitor” in the app) runs a flow suite for you on a recurring basis. Tag the flows you care about, attach the tags to a schedule, and Echopoint launches the suite without a manual trigger, a CLI call, or a CI job.
Typical uses:
- A smoke suite that keeps watch between deploys.
- A contract check against a staging API every morning.
- A recurring probe of a third-party API you depend on.
Creating a monitor
Section titled “Creating a monitor”A monitor selects flows by tag — the same tags the CLI uses for flows run --tag. The app previews which flows the current tag selection matches before you save, so you can see exactly what the schedule will run.
Pause and resume
Section titled “Pause and resume”Every monitor can be paused and resumed. A paused monitor keeps its configuration and history but launches nothing until you resume it.
Run history
Section titled “Run history”Each monitor records its own run history. Every scheduled run is a normal execution: open it to see per-node results, recorded assertions with expected vs actual, and any skip reasons.
Failure alerts
Section titled “Failure alerts”When a scheduled run fails, Echopoint emails the recipients configured on that monitor — organization members or additional addresses. The alert links to the failed run so the first click lands on the evidence.
Schedules and CI are complements
Section titled “Schedules and CI are complements”Schedules watch continuously; CI gates changes. Keep the pull-request suite in the GitHub Action and let monitors cover the time between merges.