What Counts Toward Your Credits
Your Alteryx One subscription includes a set number of Alteryx Credits (referred to as Credits). Certain workflow runs and other activities use Credits based on how they’re started, the product used, and the user’s seat type.
In most cases, one qualifying run uses 1 Credit.
Activities That Use a Credit
Scheduled workflow runs: A workflow that runs on a schedule, such as every night, uses 1 Credit each time it runs.
API-triggered workflow runs: A workflow started through an API call uses 1 Credit each time it runs.
Orchestrator runs: A plan that runs on a schedule or is triggered by an external event uses 1 Credit for the entire run, regardless of how many workflows or other assets it includes.
Viewer-initiated workflow runs: run started by a Viewer manually or through the Alteryx MCP Server, including through the
apps,designer, andlivequerytoolsets, uses 1 Credit. Workflows run locally through the Alteryx One app MCP Server don’t use Credits.Analytic app runs: An analytic app uses 1 Credit each time it runs.
Auto Insights email subscriptions: An Auto Insights report sent through a subscription or scheduled email uses 1 Credit each time the email is sent, regardless of the number of recipients.
Google Edition Accounts
Manual runs by all users count toward usage. This is because Google Edition pricing is based on usage rather than the number of user seats.
Server Design-Time Usage
Manual design-time runs by all Alteryx Server users count toward usage. Server usage is based on consumption, not the number of user seats.
Activities That Don’t Use a Credit
Runs that end in an error: Includes workflow runs that end in an error, whether the workflow or an Alteryx technical issue causes the error.
Sample data runs: Designer Cloud and LiveQuery runs that generate sample data while a workflow is being built.
Design-time runs: Manual Designer Cloud or LiveQuery runs started by Full Users or Basic Users, including runs used to build, test, or validate a workflow.
Validation runs: Metadata validation checks performed when a Designer Desktop workflow is uploaded to Server.
Auto Insights dataset refreshes: Manual or scheduled refreshes of an Auto Insights dataset.
What Happens When You Use All Your Credits
If you use all the Credits included with your subscription, contact your Alteryx account team to review your usage and discuss additional capacity.
Quick Reference
Activity | Cloud Automation* | On-Prem Automation** |
|---|---|---|
Scheduled workflow run | Uses a Credit | Uses a Credit |
API-triggered workflow run | Uses a Credit | Uses a Credit |
Scheduled plan run | Uses a Credit | Not applicable |
API-triggered plan run | Uses a Credit | Not applicable |
Full User-initiated runs | Does not use a Credit, except for Google Edition accounts. | Uses a Credit |
Basic User-initiated runs | Does not use a Credit, except for Google Edition accounts | Uses a Credit |
Viewer-initiated runs | Uses a Credit | Uses a Credit |
Analytic app run | Uses a Credit | Uses a Credit |
Auto Insights email subscription | Uses a Credit | Not applicable |
Run that ends in an error | Does not use a Credit | Does not use a Credit |
Validation run | Not applicable | Does not use a Credit |
Design-time run | Does not use a Credit | Does not use a Credit |
Sample data run | Does not use a Credit | Not applicable |
Auto Insights dataset refresh | Does not use a Credit | Not applicable |
*Cloud refers to executions in Alteryx One, including Workspace Execution, E2 Linux, and Live Query.
**On-premises refers to executions on Alteryx Server.