Automations
Schedule repeatable checks and reports without losing ownership or evidence.
Schedule repeatable checks and reports without losing ownership or evidence.
What this feature is for
Automations runs recurring operational work with retries, pause controls, and a durable run ledger. 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 narrow job purpose, cadence, owner, output channel, and a plan for what should happen when the job fails.
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
Create the task, run it once manually, inspect the output, set the cadence, and review run history before increasing frequency.
- 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 ledger records schedule, attempt, status, retry, pause, output, and last successful run. 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
A task that fails repeatedly is a configuration problem. Pause it, fix the source provider or assertion, and resume only after a manual verification.
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 Automations with Uptime, Revenue Guard, Reports, and Operator. 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.