> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

<Check>
  **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.

  See [Setting Up Data Warehouse Connections](/guides/paradime-101/getting-started-with-your-paradime-workspace/setting-up-data-warehouse-connections) and [Scheduler environment](/products/settings/connections/scheduler-environment/index).
</Check>

### 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.

<Check>
  **Solution**

  Check the production connection details.

  Test the connection again.

  If the test fails, confirm the credentials with your Snowflake admin.

  See [Snowflake](/products/settings/connections/scheduler-environment/snowflake).
</Check>

### 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.

<Check>
  **Solution**

  Check the development connection details.

  Test the connection again.

  If the test fails, confirm the credentials with your Snowflake admin.

  See [Snowflake](/products/settings/connections/development-environment/snowflake).
</Check>

### 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.

<Check>
  **Solution**

  Review the permissions on your development connection.

  Then check the setup guide for your warehouse in [Code IDE environment](/products/settings/connections/development-environment/index).
</Check>

### 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](/get-help/error-list/clear-paradime-local-storage).


## Related topics

- [Workspaces](/products/settings/workspaces.md)
- [Troubleshooting](/get-help/error-list/index.md)
- [Fix with DinoAI](/products/dino-ai/bolt-pipeline-agent/fix-with-dinoai.md)
- [Errors](/get-help/errors.md)
- [Creating a Workspace](/guides/paradime-101/getting-started-with-your-paradime-workspace/creating-a-workspace.md)