Skip to content
ayx-rsv0.15.0

Troubleshooting

Start with doctor

Section titled “Start with doctor”

Most issues surface here. doctor checks config, auth, and connectivity without changing anything:

Terminal window
ayx doctor          # config, auth, and connectivity
ayx doctor auth     # just authentication
ayx doctor network  # just connectivity

When an Alteryx One command fails

Section titled “When an Alteryx One command fails”

If a One command fails, it’s almost always the token, not the endpoint — the /v4 API is reached directly, and an expired or stale bearer token is the usual cause. Refresh your token with ayx one login, then confirm:

Terminal window
ayx doctor auth

Where to look things up

Section titled “Where to look things up”
Question Page
Does this command exist, and what are its flags? Command surface
How is configuration resolved? Runtime config contract
What’s the stable CLI contract? CLI spec

When the docs and your binary disagree

Section titled “When the docs and your binary disagree”

Trust the binary. The command reference is generated from the CLI’s own command tree and checked for staleness in CI — it isn’t rewritten automatically. Check your version with ayx --version and compare against the release notes.