Diagnostics
Two commands give you a quick read on the health of your Alteryx One environment: ayx one doctor and ayx one inventory. Run these first when something seems off, or wire them into a monitoring script.
Quick reference
Section titled “Quick reference”| Command | What it does |
|---|---|
ayx one doctor auth |
Verify authentication credentials are valid |
ayx one doctor discover |
Probe API discoverability |
ayx one doctor identity |
Check identity surface health |
ayx one doctor plans |
Check plans surface health |
ayx one doctor scheduling |
Check scheduling surface health |
ayx one inventory |
Asset inventory across the workspace |
Running a full health check
Section titled “Running a full health check”Run all doctor subcommands in sequence to get a broad picture:
ayx one doctor authayx one doctor discoverayx one doctor identityayx one doctor plansayx one doctor schedulingEach check is independent. A failure in one does not block the others.
Authentication check
Section titled “Authentication check”Start here when commands return 401 or credential errors:
ayx one doctor authThe result reports the selected workspace credential method without printing
token values, along with credential_kind, renews_automatically, and the
access-token expiry. OAuth credentials are normally renewed automatically;
email-OTP credentials are time-limited and require an interactive login when
their 30-day token expires. For an email-OTP credential the check also suggests
ayx one login --oauth-api-token — that is an upgrade to a credential that
renews itself, not a repair to a broken one. If
an OAuth refresh token is expired or revoked, re-import a newly issued pair
with ayx one login --auth-method oauth-refresh using the env/stdin input
options described in Identity & auth.
Add --profile <name> to test a specific profile:
ayx one doctor auth --profile stagingDiscovery check
Section titled “Discovery check”discover probes the API to confirm the Alteryx One endpoint is reachable and returning expected metadata:
ayx one doctor discoverIdentity, plans, and scheduling checks
Section titled “Identity, plans, and scheduling checks”These targeted checks verify that specific API surfaces are healthy:
ayx one doctor identityayx one doctor plansayx one doctor schedulingInventory
Section titled “Inventory”inventory is a standalone command (not under doctor) that provides a broader view:
# Asset inventory across the workspaceayx one inventoryAccepts --profile <name>.
The old top-level status command under one — and its nested equivalent from the former platform group — have both been removed entirely, with no direct successor. Looking for Alteryx Server health instead? That’s ayx server api status — a separate command outside the one surface.
JSON output
Section titled “JSON output”All diagnostic commands support -o json:
ayx -o json one doctor authayx -o json one inventoryThe envelope is { ok, message, timestamp_utc, data } on success; failures also include error_code. Pipe to jq for scripting:
ayx -o json one doctor auth | jq '.ok'Related
Section titled “Related”- API introspection — spec fetch and coverage diff, separate from the health checks on this page
- Connecting — how to configure profiles and credentials
- Alteryx One overview — all
ayx oneareas - Troubleshooting — common errors and fixes