Workflow usage and token history
Workflow usage and token history in AI Flowi Workflow show recorded execution steps, token charges and balance information. Ai Flowi provides Usage views for checking workflow activity, API calls and access rules. Use this guide to read the records and distinguish charged steps from complete workflow runs. Overview reads the newest 1,000 records in the selected window.
Published · Updated
Product: AI Flowi Workflow by Ai Flowi · Task: Inspect usage and token history · Components: No extra component required
When to use this
Use Usage to inspect recorded charges, compare activity within a period and check the reason shown for a failed execution.
Before you start
- Sign in and open Usage from the dashboard navigation.
- From Home, select View usage → to open Overview.
- Check your workspace selection before reading API usage or published-app information.
Workflow charge records shown here belong to the signed-in user; API call records are scoped to the selected workspace.
Steps
1. Overview
Select Period, then choose Last 30 days, Last 7 days or Today.
Review Workflow Runs, Token Balance, Success Rate and Published Webs.
Workflow Runs and Success Rate are calculated from recorded charged workflow steps, so they do not count distinct complete workflow runs.
The dashboard reads the newest 1,000 usage records in the selected window, so a busier window can have incomplete totals.
2. Workflow Runs
Read Executed At, Run ID, Workflow, Step, Tokens and Status for each recorded charge.
Each row represents one charged step; Workflow shows an identifier and Duration shows a dash because the log stores neither the workflow name nor run duration.
Use the page controls to move through the loaded records.
3. Token Usage
Check Total Token Balance, the amounts on hold and available, and Valid Until.
Used This Month covers the current calendar month and subtracts recorded token credits from charges, independently of the selected Period.
Read Source, Change, Balance After and Reason in Token Ledger for the selected period.
Token Ledger uses execution records; it is not a payment history, and Last Payment has no recorded payment value.
API Hub can hold tokens during a call and settle the recorded charge or release the hold afterward.
4. API Usage
Review API / Node, Type, Access, Max Tokens / Call, Usage and Current Source.
Usage counts API Hub calls for the selected period, while Access and Current Source show the effective access rule.
Use the API Hub guide for managed API settings and key configuration.
5. Product Usage
Review Runs and Published Web Apps, then inspect Publish Web Usage for the displayed domain and published-app count.
Flows Created, Nodes Created and creation averages are sample values, so do not use them as measured account activity.
6. Ask AI Usage
Open Ask AI Usage to inspect any recorded Ask AI charges, including Scope, Action, Tokens and Status.
The view groups recorded entries into Canvas and Node; an empty charge history does not establish whether you used Ask AI.
7. Run History
Review Time, Execution, Type, Tokens, Status and Error for the selected period.
Failed rows show the recorded reason, or “No error text recorded.” when no reason is stored.
Duration is not recorded, and this view provides pagination rather than an export or retry control.
8. API & Node Access
Open API & Node Access in the account navigation to inspect Access, Max Tokens / Call and Rule Source, then read Plan limits.
Call Limit shows a dash because the effective API rule does not supply a monthly call limit.
Subscriptions
In the workflow account screen, open Subscriptions and check Current Subscription for your plan, status, available tokens and validity.
Use the status filter to inspect subscription records without treating execution charges as subscription payments.
The account Usage tab also provides Usage Logs with sortable execution and token-balance columns.
Common mistakes
- Do not treat charged-step counts as distinct complete workflow runs.
- Do not use sample creation values, a missing duration or Last Payment as measured records.
- Do not interpret an unavailable service response as zero usage.
Troubleshooting
If the balance or usage log is unavailable on Home, use its retry control to request the data again.
If “Runs are refused right now” appears, read the displayed billing reason before trying another execution.
If “Call counts unavailable” appears, check the displayed API Hub error before interpreting the count.
Related
Documentation · AI Flowi Workflow · API Hub · Workspaces · Publishing · Publish a workflow as a web app · Pricing · Book a demo