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.Solution
- Add an active production connection for the scheduler.
- Confirm the connection works before rerunning.
- If you use a custom target, confirm that target exists.
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.
SolutionCheck the production connection details.Test the connection again.If the test fails, confirm the credentials with your Snowflake admin.See Snowflake.
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.
SolutionCheck the development connection details.Test the connection again.If the test fails, confirm the credentials with your Snowflake admin.See Snowflake.
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.
SolutionReview the permissions on your development connection.Then check the setup guide for your warehouse in Code IDE environment.