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

# Usage and billing

> Understand run credits, pay-as-you-go usage, seats, and billing failures.

Usage and billing are managed per project. A project's run credits are used
first; after they are gone, an active pay-as-you-go subscription allows
billable workflows to continue running.

The current pay-as-you-go rate shown in WorkflowDog is **$1 per 100 workflow
runs**, or **$0.01 per run**. A run can contain any number of actions.

## How a run is charged

When WorkflowDog receives a billable run:

1. It checks whether the workflow is Live.
2. It uses one project run credit when a credit is available.
3. If no credits remain, it checks for an active project subscription.
4. With valid usage billing, it records a \$0.01 usage charge.
5. Without valid billing, it marks the run Failed instead of executing it.

<Note>
  New projects currently begin with 100 introductory workflow-run credits. The
  current balance appears under **Usage & Billing**.
</Note>

The **Callable Workflow** trigger does not consume a credit or create a usage
charge. It is the current free trigger type. The Usage page can still include
free and failed runs in activity counts even when they contribute no cost.

## Credits before pay-as-you-go

Run credits are always depleted before paid usage accrues. Connecting a
subscription does not discard the remaining balance.

When a project has neither credits nor usable pay-as-you-go billing, billable
runs fail with:

```text theme={null}
The project is out of workflow runs and isn't set up for usage billing.
```

Enable billing, then send a new trigger event or
[re-run](/essentials/workflow-runs#re-run-with-the-same-trigger-data) a saved
payload. The failed run is not resumed automatically.

## What counts as a run

Billing eligibility is decided when the run is queued, before its nodes
execute. Therefore:

* A run that later completes with a node error still consumes its reserved
  credit or paid usage.
* A run that fails the initial Paused, out-of-credit, or invalid-payment check
  does not execute nodes.
* A Scheduled run reserves its credit or usage when it is scheduled.
* Cancelling a Scheduled run restores its credit or reverses its usage charge.
* The number of actions in the graph does not change the per-run price.

<Warning>
  A Completed run can contain node errors and still be billable. Use the cost
  card for billed usage and run history for execution quality; the raw run count
  is not the same as the bill.
</Warning>

## Enable pay-as-you-go

<Steps>
  <Step title="Open Usage & Billing">
    Choose the project, then open **Usage & Billing** from the dashboard.
  </Step>

  <Step title="Review the current balance">
    Check **Workflow Run Credits**, the current billing period, and recent usage
    by workflow.
  </Step>

  <Step title="Upgrade">
    Select the upgrade option and complete the hosted checkout. Billing belongs to
    this project only.
  </Step>

  <Step title="Confirm usage is allowed">
    Return to the project and confirm the billing warning is gone. Live
    billable workflows can now continue after credits reach zero.
  </Step>
</Steps>

Only an Editor can start checkout or open the billing-management portal.

## Read the Usage & Billing page

The page includes:

| Section                   | Meaning                                                                |
| ------------------------- | ---------------------------------------------------------------------- |
| **Usage Cost**            | Sum of paid run charges in the selected billing period.                |
| **Workflow Run Credits**  | Prepaid or introductory runs remaining before paid usage accrues.      |
| **Team Members**          | Accepted project members compared with the project's seat allowance.   |
| **Breakdown by Workflow** | Run activity attributed to each workflow, including deleted workflows. |

Use the period arrows to inspect an earlier billing period. A future period
cannot be selected.

Deleted workflows can remain in the breakdown because project-level run
records are preserved for usage tracking.

## Manage the subscription

When the project has an active subscription, **Manage** opens the billing
portal. Use it to update the payment method or subscription.

If WorkflowDog cannot accrue new usage, the project shows a billing warning and
new billable runs fail with:

```text theme={null}
The payment is invalid.
```

Fix the payment issue in the billing portal. Existing failed runs remain in
history; send a new event or re-run them after billing is healthy.

## Team seats

Seats are also tracked per project. When accepted members reach the seat
allowance, Editors cannot send another invitation.

Removing a member frees a seat. For a larger team plan, use the contact link
shown on **Usage & Billing**.

## Troubleshooting

<AccordionGroup>
  <Accordion title="The run count is higher than the billable usage">
    Activity counts can include free Callable Workflow runs and runs that
    failed before billing. Use **Usage Cost** for the amount accrued, not the
    total activity count alone.
  </Accordion>

  <Accordion title="A failed node still used a credit">
    Credits and usage are reserved when the run is accepted, before node
    execution. A node-level error does not refund the run automatically.
  </Accordion>

  <Accordion title="I cancelled a Scheduled run">
    Cancellation restores a credit-backed run or records a negative usage
    adjustment for a paid run. The history row remains with Cancelled status.
  </Accordion>

  <Accordion title="The project has a subscription but runs say payment is invalid">
    Open the billing portal and resolve the payment issue. A subscription
    identifier alone is not enough; the project must also be allowed to accrue
    usage.
  </Accordion>
</AccordionGroup>