Run the doctor
When something goes wrong, start withneetoengage doctor. It checks your authentication, API connection, and CLI version.
Common errors
When a command fails, it prints an error message to standard error and exits with status 1. Usage errors such as an unknown flag or a missing argument addRun 'neetoengage --help' for usage.
Not authenticated. Run 'neetoengage login' to authenticate.
Not authenticated. Run 'neetoengage login' to authenticate.
Problem: no workspace is signed in.
Solution: run
Solution: run
neetoengage login --subdomain <name>.Multiple subdomains authenticated (acme, beta); specify --subdomain.
Multiple subdomains authenticated (acme, beta); specify --subdomain.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add
Solution: add
--subdomain <name> to the command. For logout, --all signs out of every workspace.Not authenticated for "foo". Authenticated subdomains: acme, beta.
Not authenticated for "foo". Authenticated subdomains: acme, beta.
Problem: the
Solution: use one of the listed subdomains, or sign in to the new one.
--subdomain value does not match any signed-in workspace. Solution: use one of the listed subdomains, or sign in to the new one.
Subdomain not found. Please check that you entered the correct subdomain.
Subdomain not found. Please check that you entered the correct subdomain.
Problem:
Solution: use the first part of your workspace URL. For
neetoengage login could not find a workspace at <subdomain>.neetoengage.com. Solution: use the first part of your workspace URL. For
https://spinkart.neetoengage.com, enter spinkart.Authentication session expired. Please try again.
Authentication session expired. Please try again.
Problem: the browser sign-in was not approved before the session expired.
Solution: run
NeetoEngage CLI authentication timed out after 5 minutes. Please try again. means the CLI stopped waiting. Solution: run
neetoengage login again and approve the sign-in in the browser. If the browser does not open, visit the URL the CLI prints.Could not connect to NeetoEngage. Check your internet connection
Could not connect to NeetoEngage. Check your internet connection
Problem: the CLI could not reach the API.
Solution: check your network and run
Solution: check your network and run
neetoengage doctor. If NEETOENGAGE_BASE_URL is set, confirm it points at a reachable server.required flag(s) "xxx" not set
required flag(s) "xxx" not set
Problem: a required flag was omitted.
Solution: check the command’s reference page or run
Solution: check the command’s reference page or run
neetoengage <command> --help for the required flags.API error (422): <message>
API error (422): <message>
Problem: the server rejected the request. The CLI prints
Solution: follow the suggestion. For 401, run
API error (<status>): <message>, one line per additional error, and a Suggestion: line for common statuses: 401 (sign in again), 403 (no permission), 404 (check the ID), 422 (check required fields with --help), and 429 (rate limited, wait and retry). Solution: follow the suggestion. For 401, run
neetoengage login to refresh the session.Claude Code not found (~/.claude/ does not exist).
Claude Code not found (~/.claude/ does not exist).
Problem:
Solution: install and open Claude Code, then run the command again.
neetoengage setup claude requires Claude Code to have been run at least once. Solution: install and open Claude Code, then run the command again.
Known API responses
Some requests fail with a NeetoEngage-specific message:Check the version
neetoengage update.