[Catalog](https://skills.polygres.com/index.md) / [polygres-troubleshooting](https://skills.polygres.com/polygres-troubleshooting/SKILL.md)

Published skills release: 0.9.0. [Compatibility and source](https://skills.polygres.com/manifest.json).

Scripts and templates mentioned here require the installed package; reading this page does not install them.

# Context and connectivity

Confirm the installed contract and local context before interpreting a remote
failure.

```console
polygres --version
polygres --help
polygres config path
polygres --json whoami
polygres --json projects list
python -c 'from importlib.metadata import version; print(version("polygres-cli")); print(version("polygres-sdk"))'
```

Use command-specific help for every later command. Record CLI version, exit
code, SDK version, and sanitized stderr. For a live test from a Polygres source
checkout, verify both packages were reinstalled from that checkout into an
isolated environment and confirm their import origins before interpreting a
remote failure. Do not diagnose checkout code through stale PyPI packages. Do
not print environment variables or config-file contents because they may expose
an API key or other credential.

Classify `whoami` failures as local configuration, expired or absent
authentication, network reachability, or control-plane response errors. Do not
convert an authentication failure into a project-not-found diagnosis.

Select an exact project ID from the public list or an explicit user-provided
value. If names collide, input is fuzzy, or configuration and user input
disagree, report an ambiguous project and stop. Never fuzzy-match a project.