Activity
Keep a durable sequence of changes, checks, incidents, and evidence.
Keep a durable sequence of changes, checks, incidents, and evidence.
What this feature is for
Activity is the shared history that lets a team understand what happened before and after a release or incident. 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 workspace with checks, deployments, provider changes, or incidents; the useful work is naming actions clearly.
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
Filter the timeline by app or event type, open the originating record, and add the link to the release or incident review.
- 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
Each event should retain actor, timestamp, object, outcome, and a link back to the full 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
If a change is missing, verify whether it happened outside PreFlight and record the external reference rather than rewriting the history.
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 Activity with every outcome hub, especially Deploy, Revenue, and Incidents. 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.
