Skip to main content

Why usage should be reviewed regularly

Usage tells you whether your workflows are operating at the scale you expect. It helps you spot:
  • workflows that fire too often
  • AI-heavy workflows that are more expensive than expected
  • workspaces that are approaching subscription plan limits

Two main usage categories

The product tracks:
  • run credits
  • AI credits
These represent different kinds of activity and should be monitored together, not separately.

Limits are part of workflow design

Usage is not only something to check after a workflow is live. It should influence how you design workflows from the beginning. For example:
  • frequent schedules should be intentional
  • long step chains should justify their value
  • AI should be used where it clearly improves the result

What to monitor over time

Check usage when:
  • a workflow is new
  • a schedule changes
  • AI usage increases
  • a workflow starts running more often than expected
This helps you catch issues before they become expensive or disruptive.

Where limits show up in practice

Plan limits can affect:
  • how much workflow activity the workspace can sustain
  • how many live workflows can be published
  • how much history is retained
  • how long workflows can run
If a workflow becomes operationally important, its usage profile is worth monitoring just as closely as its outputs.