> ## Documentation Index
> Fetch the complete documentation index at: https://parabola.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Can I see how many credits a specific flow run used?

> There's no built-in report broken down by individual run. Here are the closest options available today.

Not precisely — Parabola doesn't have a report that shows credit usage for one individual run. Here's the closest you can get today.

## Option 1: Check the balance before and after

Note your credit balance on the [Billing](https://parabola.io/app/billing) page, run the flow once, then check the balance again. The difference is that run's credit cost. The counter updates in real time, so this works well for a single one-off run. See [Understanding and Managing Credit Usage in Flows](/docs/articles/understanding-and-managing-credit-usage-in-flows) for how each step type is priced (a flat 10 credits for standard steps, 20–80 for Prowork-built steps depending on complexity, and variable amounts for other AI steps).

## Option 2: Per-flow and per-user totals (admins, Usage Reports)

Admins can use [Usage Reporting & Analytics](/docs/product/account/usage-reporting-analytics) (on the Billing page) for a **Flow Report** showing total runs and total credits **per flow** over the last 30 days, and a **User Report** with the same broken out **per user**. This is aggregated across all of a flow's runs in the window, not a single-run figure, and updates once daily (approximately 3am ET for the prior day) — so it's the right tool for spotting which flow is driving usage, not for pinpointing one run.

## If usage seems higher than expected

A common cause is a flow running more often than intended — for example, an email-triggered flow set to **Run the flow once per attachment**, or one that isn't restricted to a single file type with **Only process \[file type]**, can multiply the number of runs (and credits) per email received. Check the flow's **Run History** for an unexpectedly high run count before assuming a billing error.

If the run count looks right but usage still seems off, contact [help@parabola.io](mailto:help@parabola.io) with the flow link and time range — support can review it with you.

## Related

* [Understanding and Managing Credit Usage in Flows](/docs/articles/understanding-and-managing-credit-usage-in-flows)
* [Why was I charged credits for a flow run where a step failed?](/docs/articles/why-was-i-charged-credits-for-a-run-where-a-step-failed)
* [Extract from email](/docs/product/integration/extract-from-email)