Usage and Metering
Flow records task execution usage separately from on-chain gas. The usage view groups activity and spend by the workspace/project context and selected time period. Exact prices and plan allowances come from the active plan and billing configuration.
Compute
On a confirmed run, the pipeline records compute time from acceptance through submission and adds successful receipt-callback runtime where applicable. Usage reporting is keyed to execution identity to avoid double counting normal retries.
Task skips and cloud simulations do not follow the confirmed-run compute billing path. A failure callback that actually runs can report its own compute usage. A confirmed transaction remains confirmed even when later callback or storage processing fails.
Reduce work by reading only what you need, bounding HTTP calls, and skipping as soon as the decision is clear.
RPC-related usage
Local thyme run reports RPC activity from its own instrumented client. The current cloud execution's rpcCalls value instead uses the number of returned/submitted contract calls as a proxy, and overage reporting uses that value with the plan's allowance.
These numbers are not equivalent. Do not interpret the cloud submitted-call metric as a count of all ctx.client reads or use it as precise network telemetry. Keep reads efficient, but evaluate actual bills against the deployment's recorded metrics and plan.
Gas
| Scenario | Source of gas payment |
|---|---|
| Sponsored testnet | Configured sponsorship; no dBank debit. |
| Sponsored mainnet, where supported by an enabled provider/profile route | Workspace dBank. The current Roles/Lift route is Sepolia-only. |
| Wallet-paid legacy | Profile's native balance; USD conversion is for display. |
| Wallet-paid testnet | Profile's native test-token balance. |
Managed Lift operations settle through Lift rather than a second Flow debit; current Roles/Lift support is Sepolia-only. A transaction revert can still incur gas. Gas units, native-token cost, USD value, and dBank debit are different fields; settlement may complete after a submission response. See dBank.
Review usage
Use the console's usage summary, gas history, function attribution, and transaction ledger. Compare the effective gas mode of a run with its executable's default, especially when fallback was enabled.
Billing-role access does not grant permission to operate tasks or read all operational pages. See console roles and API authorization.