How it works
Outcomes and alerts
Passed, broken, uncertain, flaky, and when Mystra pages you.
Updated
Outcomes
| Outcome | Meaning | Alerts? |
|---|---|---|
| Passed | All four steps proved. | Recovers an open alert. |
| Broken | A proven break: a 4xx or 5xx, a timeout, a missing email, a closed paid area. | Yes, with the proof attached. |
| Uncertain | Something did not go to plan but nothing was proven, for example no upgrade button was found. | No. Three in a row earn one “needs a look” note per day. |
| Flaky | Passed only on a retry. Signup, email and access are retried once; pay never is. | No. |
How alerts behave
A broken run opens an alert on your channels: a Slack incoming webhook, an email address, or a JSON webhook. While it stays broken you get a reminder at the interval you choose; quiet hours hold Slack and email. The moment the same step passes again, the alert recovers by itself and you are told once more. That is two messages per incident.
Channels and rules live under Alerts. There is no threshold to tune: Mystra only alerts on what it can prove.
Webhook payload
A JSON webhook channel receives type (alert.open, alert.recovered, alert.attention or alert.test), the app's name and host, and the alert: status, step, environment, proof, message, and the run that broke or fixed it, with its id for a link.