Incidents & fixes
Give every failure an owner, a recovery path, and a verification step.
Give every failure an owner, a recovery path, and a verification step.
What this feature is for
Incidents & fixes turns failed checks, attacks, and user-impacting signals into an owned response loop. It keeps the original evidence attached while the team works. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
A detected issue, a responder, and a clear definition of what a recovered state looks like.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Acknowledge the incident, assign an owner, open recovery guidance, document the correction, rerun the check, and close only when the evidence is green.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
The incident record preserves severity, timestamps, source signal, changes, and verification evidence. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
Do not close an issue because the alert stopped. Confirm the underlying monitor, journey, or provider probe passes again and record the deployment or provider change that fixed it.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Incidents with Health, Alert delivery, Runbooks, and Activity. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.