For the complete documentation index, see llms.txt. This page is also available as Markdown.

Workspace and warehouse errors

Common Paradime errors related to workspace setup, warehouse connections, and local browser state.

Use this page for errors tied to connections, warehouse metadata, or local workspace state.

PARA-1000: Missing production warehouse connection

This error appears when you run a production dbt job in Bolt without an active production warehouse connection.

It also appears when your production run references a target that does not exist.

PARA-1007: Couldn't fetch info-schema from Snowflake for production catalog

Paradime could not fetch the information schema for your production catalog.

Common causes include:

  • The production user does not exist.

  • The stored credentials are invalid.

  • The Snowflake account no longer exists or has expired.

PARA-1007: Couldn't fetch info-schema from Snowflake for dev catalog

Paradime could not fetch the information schema for your development catalog.

Common causes include:

  • The development user does not exist.

  • The stored credentials are invalid.

  • The Snowflake account no longer exists or has expired.

PARA-1014: Couldn't list databases when running paradime sources generate

Paradime could not list databases to generate sources.yml.

This usually means your development connection does not have enough access to query information schema.

PARA-1015: Clear Paradime local storage

Some UI issues come from stale local browser data.

For the full reset steps, see Clear Paradime local storage.

Last updated

Was this helpful?