Skip to content
Komodo SDK

Troubleshooting

Authentication and credentials

Section titled “Authentication and credentials”

”Not authenticated” / login loops

Section titled “”Not authenticated” / login loops”

Run:

Terminal window
uv run komodo login

Complete the browser OAuth flow. If you use multiple Komodo environments, set KOMODO_ENVIRONMENT to integration or production consistently for both CLI and SDK (see Authentication).

Wrong or missing account (UnsetAccountError)

Section titled “Wrong or missing account (UnsetAccountError)”

You may see: An account_id was not passed and could not be read from the SDK client session.

  1. Run
    Terminal window
    uv run komodo account set
    and pick an account.
  2. Or pass account_id= into get_snowflake_connection(...) (and JWT or M2M credentials as needed).

See Accounts.

Custom credentials file path

Section titled “Custom credentials file path”

If you use KOMODO_CREDENTIALS_PATH, the CLI and SDK must agree on the same path. See Credentials file configuration.

M2M: ValueError about JWT vs client secret

Section titled “M2M: ValueError about JWT vs client secret”

You cannot pass both jwt and client_id/client_secret. Use one auth mode only. See Authentication types.

Snowflake and queries

Section titled “Snowflake and queries”

Connection works but queries fail (database / role / syntax)

Section titled “Connection works but queries fail (database / role / syntax)”
  • Run USE DATABASE, USE SCHEMA, and USE ROLE as required for your account. Examples use DATA and roles your admin assigned.
  • Prefer starting with INFORMATION_SCHEMA queries from the Quickstart and Executing Queries guides.

Long-running or blocked queries

Section titled “Long-running or blocked queries”

Use Async Queries with execute_query_async for submit-and-poll flows. Remember blocking I/O behavior described there.

Pandas warnings

Section titled “Pandas warnings”

If pandas warns about non-SQLAlchemy connectables, the connection is still valid. See Pandas Integration.

MCP server

Section titled “MCP server”

MCP cannot find komodo or fails to start

Section titled “MCP cannot find komodo or fails to start”
  • cwd in MCP config must be the project directory where uv can run komodo (directory with pyproject.toml that depends on komodo).
  • Use the same command / args as in MCP Server (uv run komodo mcp run).

Wrong environment in the assistant

Section titled “Wrong environment in the assistant”

MCP subprocesses do not inherit your shell. Set KOMODO_ENVIRONMENT in the MCP env block if you need integration.

Schema exploration fails but CLI works

Section titled “Schema exploration fails but CLI works”

Re-run

Terminal window
uv run komodo account set
and confirm the account matches what you expect. In Komodo internal environments, extra MCP tools may be available when internal extensions are installed.

Installation

Section titled “Installation”

Python version errors

Section titled “Python version errors”

The SDK requires Python 3.10+. See Installation.

Still stuck?

Section titled “Still stuck?”