Skip to main content

​
Run the doctor

When something goes wrong, start with neetoplaydash doctor. It checks your authentication, API connection, and CLI version.
When multiple workspaces are signed in, name the one to check:

​
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 add Run 'neetoplaydash --help' for usage.
Problem: no workspace is signed in.
Solution: run neetoplaydash login --subdomain <name>.
Problem: more than one workspace is signed in, so the target is ambiguous.
Solution: add --subdomain <name> to the command. For logout, --all signs out of every workspace.
Problem: the --subdomain value does not match any signed-in workspace.
Solution: use one of the listed subdomains, or sign in to the new one.
Problem: neetoplaydash login could not find a workspace at <subdomain>.neetoplaydash.com.
Solution: use the first part of your workspace URL. For https://spinkart.neetoplaydash.com, enter spinkart.
Problem: the browser sign-in was not approved before the session expired. NeetoPlaydash CLI authentication timed out after 5 minutes. Please try again. means the CLI stopped waiting.
Solution: run neetoplaydash login again and approve the sign-in in the browser. If the browser does not open, visit the URL the CLI prints.
Problem: the CLI could not reach the API.
Solution: check your network and run neetoplaydash doctor. If NEETOPLAYDASH_BASE_URL is set, confirm it points at a reachable server.
Problem: a required flag was omitted.
Solution: check the command’s reference page or run neetoplaydash <command> --help for the required flags.
Problem: a required flag or positional argument was passed as an empty string, usually from an unset shell variable.
Solution: check that the variable holds the id you expect.
Problem: the server rejected the request. The CLI prints 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 neetoplaydash login to refresh the session.
Problem: insights show received a --start-date or --end-date that is not YYYY-MM-DD. When --start-date is older than the most recent 3 months, the message is Insights are available only for the most recent 3 months with the earliest date you can use.
Solution: pass dates as YYYY-MM-DD, with --start-date inside the most recent 3 months.
Problem: list commands are paginated and return one page by default.
Solution: raise --page-size (max 50 for projects list and runs list, 100 for test-entities list) or walk the pages with --page. See Pagination.
Problem: a test entity id must name an entity that the given run recorded. An entity that ran only in other runs is refused.
Solution: confirm the id with neetoplaydash test-entities list <run_id> --project <project_id>.
Problem: neetoplaydash setup claude requires Claude Code to have been run at least once.
Solution: install and open Claude Code, then run the command again.

​
Check the version

Prints the CLI version, commit hash, and build date - useful when reporting an issue. To upgrade, run neetoplaydash update.