Skip to main content
Select a symptom to see the likely cause and what to do.
Likely cause: ~/.local/bin, where the CLI installs, is not on your system PATH.What to do: Add ~/.local/bin to your PATH, then open a new terminal and run condense --help. See Install.
Likely cause: The CLI is not signed with an Apple Developer ID yet, so macOS Gatekeeper blocks the first run.What to do: Clear the quarantine flag once:
Likely cause: Your session may have ended, or you signed out.What to do: Run condense auth status. If you are not signed in, run condense auth login. To sign in again, run condense auth login --force. See Sign in.
Likely cause: The CLI remembers your selection between commands, and a different one is selected.What to do: Run condense environment current and condense workspace current to see what is selected. Then select the right ones with condense environment use and condense workspace use, or name the workspace for that command with --workspace. See Environments and workspaces.
Likely cause: The name is spelled differently, or you are in a different environment.What to do: Run condense workspace list or condense pipeline list to see the exact names in the active environment and workspace.

​
Still stuck?

Contact your Condense administrator for anything about access, roles or environments. For anything else, contact Condense support.