Usage
Understand plan limits and consumption before a workflow is interrupted.
Understand plan limits and consumption before a workflow is interrupted.
What this feature is for
Usage shows the workspace’s allowances and current consumption for checks, monitoring, AI, journeys, exports, and other metered capacity. 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 plan, the billing period, and a decision about which workflows are business-critical.
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
Review current usage, identify the fastest-growing allowance, and adjust cadence or plan before a critical automation reaches its limit.
- 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
Usage evidence includes plan, period, consumed amount, remaining allowance, and the source feature. 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 silently reduce a critical monitor to solve a limit. Make the tradeoff explicit and confirm the new cadence is still useful.
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 Usage with Automations, Pricing, and the feature that is consuming the allowance. 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.