Skip to main content

Storage Mapping Deployment Failures

Storage Mapping deployment failures happen when your Environment can't properly connect to target databases and schemas. This guide covers the "No schema found" error, its causes and fixes, plus other common storage mapping issues.

The "No Schema Found" Error​

You may see this error during deployment:

No schema found for location [STORAGE_LOCATION] using database [DATABASE] and schema [SCHEMA] on [platform]. Please contact support for assistance.

This error usually occurs when an object in your Project previously referenced a different schema location, and that schema has since been deleted. During deployment, Coalesce attempts to clean up objects from their old locations. If the previous schema no longer exists, presync cannot find it and deployment fails.

Causes​

Schema Does Not Exist in the Data Platform​

Coalesce expects the schema to exist in the target database. If it was never created or was dropped outside Coalesce, presync cannot find it.

  • Typical cases: New Storage Location, schema dropped in Snowflake, schema renamed or moved.
  • How to confirm: In Snowflake, run SHOW SCHEMAS IN DATABASE <database_name>; and verify the schema exists.

Missing or Insufficient Permissions​

The service account used by Coalesce may not have access to the schema. Snowflake returns no schema when the role lacks USAGE on the database or schema.

  • Typical cases: New environment, role changes, schema created by another role.
  • How to confirm: Run the same SHOW SCHEMAS query as the Coalesce service account or role.

Trailing or Leading Whitespace in Storage Mappings​

Schema names entered manually (for example, using the override toggle) can include invisible spaces. Coalesce looks for the exact string, so MY_SCHEMA with a trailing space does not match MY_SCHEMA.

  • Typical cases: Manual override of database or schema in Storage Mappings, copy-paste from docs or emails.
  • How to confirm: Inspect the mapping value character by character or re-type the schema name.

Invalid or Placeholder Values in Storage Mappings​

Mappings can use placeholders like "N/A", empty strings, or incorrect database or schema names.

  • Typical cases: New Environment before mappings are set, mappings copied from a template, typos.
  • How to confirm: Check Build Settings → Environments → Storage Mappings for each Storage Location.

Orphaned Storage Locations​

The database or schema was dropped in the platform but is still referenced in Environment mappings. Coalesce tries to use a location that no longer exists.

  • Typical cases: Schema or database cleanup, migration, environment reset.
  • How to confirm: Compare Storage Mappings to what exists in the data platform.

Workspace versus Environment Mapping Mismatch​

Workspace Storage Mappings are for development only. Deployment uses Environment mappings. If Environment mappings are missing or wrong, deployment fails even when the Workspace looks correct.

  • Typical cases: First deploy to a new Environment, Environment not configured after Workspace setup.
  • How to confirm: Check Deploy tab → Environment → Storage Mappings for the target Environment.

Uncommitted Storage Mapping Changes​

Storage mapping changes must be committed to version control before deployment. Uncommitted changes are not used at deploy time.

  • Typical cases: Mapping updated in the UI but not committed, deployment from a different branch or commit.
  • How to confirm: Open the Git modal and ensure all mapping changes are committed and pushed.

Internal Metadata or Caching Issues (Rare)​

In some cases, updating mappings does not resolve the error. Internal metadata may be out of sync.

  • Typical cases: Complex migration, schema or location changes, prior failed deployments.
  • How to confirm: After ruling out the above causes, this is usually identified with support.

Fixes​

Create the Schema in the Data Platform​

If the schema is missing:

  1. In Snowflake (or your platform), create the schema:

    CREATE SCHEMA IF NOT EXISTS <database_name>.<schema_name>;

  2. Grant the Coalesce service account USAGE on the database and schema.

  3. Retry deployment.

Grant Permissions to the Service Account​

  1. Identify the role used by the Coalesce connection for that Environment.

  2. Grant:

    GRANT USAGE ON DATABASE <database_name> TO ROLE <coalesce_role>;
    GRANT USAGE ON SCHEMA <database_name>.<schema_name> TO ROLE <coalesce_role>;

  3. Add any other privileges needed for the objects Coalesce will create (for example, CREATE TABLE, SELECT on sources).

  4. Retry deployment.

Remove Whitespace from Storage Mappings​

  1. Go to Build Settings → Environments and select the target Environment.
  2. Open Storage Mappings.
  3. For the affected Storage Location, re-enter the database and schema names (do not copy-paste).
  4. Ensure there are no leading or trailing spaces.
  5. Save and commit the changes.
  6. Retry deployment.

Correct Invalid or Placeholder Values​

  1. Go to Build Settings → Environments → Storage Mappings.
  2. For each Storage Location, set valid database and schema values that exist in the platform.
  3. Remove or fix any mappings using "N/A", empty strings, or incorrect names.
  4. Save and commit.
  5. Retry deployment.

Update or Remove Orphaned Storage Locations​

  1. In the platform, confirm which databases and schemas exist.
  2. In Build Settings → Environments → Storage Mappings, compare each mapping to the platform.
  3. For mappings that point to dropped locations:
    • Update to the new database or schema if the objects were moved.
    • Remove the mapping if the location was intentionally deleted.
  4. Save and commit.
  5. Retry deployment.

Configure Environment Storage Mappings​

  1. Go to the Deploy tab.
  2. Select the target Environment.
  3. Open Storage Mappings for that Environment.
  4. Map every Storage Location used by your Nodes to the correct database and schema for that Environment.
  5. Save and commit.
  6. Retry deployment.

Commit Storage Mapping Changes​

  1. Open the Git modal (version control).
  2. Confirm all Storage Mapping changes are staged and committed.
  3. Push to the remote if your deployment uses the remote branch.
  4. Retry deployment.

Contact Support (When Self-Service Fixes Fail)​

If you have:

  • Verified the schema exists and the service account has permissions
  • Confirmed Storage Mappings are correct and committed
  • Removed whitespace and invalid values
  • Checked for orphaned locations

and the error persists, contact support@coalesce.io with:

  • Full error message
  • Deployment ID
  • Storage Location name and database or schema from the error
  • Steps you've already tried

Other Storage Mapping Issues​

The following issues can also cause deployment failures. They are covered in the Causes and Fixes sections above, or are distinct scenarios.

Overlapping Database and Schema Mappings​

When your development Workspace and deployment Environment point to the same database or schema, you'll see conflicts and unexpected behavior.

  • How to fix: Use different databases and schemas for each Environment. For example, use DEV_DB for development, QA_DB for testing, and PROD_DB for production.

Location Added in Failed Deployment​

When a new Node adds a Storage Location and deployment fails before that change is applied, the location is never created in the target Environment. Later deployment plans may fail because Coalesce expects the mapping to exist, but it was never added.

  • How to fix: Add the missing Storage Location mapping to the Environment in Build Settings → Environments → Storage Mappings with valid database and schema values. Redeploy to apply the change.

Missing Storage Location Definitions​

This happens when Storage Locations exist in your Workspace but aren't defined in the target Environment mappings.

  • How to fix: Make sure all Storage Locations used in your Nodes are defined in the target Environment's Storage Mappings with valid database and schema references.

Deployment Plan Generation Failures​

The deployment process validates Storage Mappings at multiple stages. A failure at any stage stops the entire deployment.

  • How to fix: Review deployment plan errors carefully. Fix any Node configuration issues, circular dependencies, or invalid references before trying again.

Clearing Metadata​

In some cases, clearing the Environment metadata can help resolve persistent schema reference issues. If you suspect stale metadata, contact support@coalesce.io for guidance on clearing it.

Prevention​

To reduce storage mapping failures:

  • Create databases and schemas before adding Storage Locations or deploying.
  • Use consistent naming and avoid manual override when possible.
  • Grant the Coalesce service account the required privileges on databases and schemas.
  • Commit Storage Mapping changes before deploying.
  • Prefer managing objects through Coalesce instead of dropping or renaming them directly in the platform.

Best Practices​

Follow these practices when configuring Storage Mappings:

  • Separate Environment Mappings: Each Environment (DEV, QA, PROD) should map to completely different databases and schemas to avoid conflicts.
  • Commit Storage Changes: Always commit Storage Mapping changes to version control before attempting deployment.
  • Verify Database and Schema Existence: Make sure target databases and schemas exist with proper permissions before deployment.
  • Use Consistent Storage Location Names: Storage Location names should be the same across all Environments. Only the database and schema mappings should differ.

What's Next?​