Usage and tasks
Flowmage counts what your runs use in tasks: one attempt at one step. See this month's tasks for Test and Prod, and how your workspace's runs went.
Why it matters
Your plan includes a number of tasks a month for Prod and for Test, listed on Limits. Usage shows how far into them you are, and which flows, nodes and connections use the most.
How it works
A retry is another attempt, so another task; a step the run never reaches costs none. Prod and Test each have their own pool.
| Where | What it shows |
|---|---|
| The usage tile, at the foot of the sidebar | This month's tasks on Prod and on Test, each against your plan. |
| Settings, then Workspace, then Usage | For the environment you are on: runs, how many succeeded, average duration and queue wait; the node types, connections and tables used; recent runs; file storage. The range in the top bar starts at Last 30 days. |
| Settings, then Organization, then Settings | Your plan, its Seats, and Tasks this month on Prod and on Test. |
An example
A flow sends an invoice, then records it in a table. A run that sends it at the first attempt uses one task per node. A run whose first send fails and whose retry works uses one more. A run that fails at the invoice never reaches the table node, which costs nothing.
Limits
- Your plan is managed through support, not in Flowmage.
- Only workspace admins see the workspace's Usage; only the organization's owners and admins see its Settings.
- The workspace's usage shows one environment at a time; file storage counts both.