Troubleshooting Connectivity

Invalid Account Configuration

Error Message

Invalid Snowflake account identifier provided.

Cause

The account identifier is incorrect or not in the expected format.

Common mistakes:

• using full URL instead of account identifier
• incorrect region or cloud suffix
• missing organization name (for newer accounts)

How to Fix

Verify the account identifier in Snowflake.

Correct formats

xy12345
xy12345.us-east-1
orgname-accountname

Steps

1. Log in to Snowflake
2. Copy the account identifier from the URL
3. Ensure only the account identifier is used (not the full URL)

Warehouse Issues

Error Message

Failed to check if warehouse "Q" can be used.

Cause

The warehouse:

• does not exist
• is suspended and cannot be resumed
• user does not have access
• insufficient permissions on warehouse

How to Fix

Step 1: Verify warehouse exists

SHOW WAREHOUSES;

Step 2: Grant usage permission

GRANT USAGE ON WAREHOUSE <warehouse_name> TO ROLE <role_name>;

Step 3: Ensure warehouse is running

ALTER WAREHOUSE <warehouse_name> RESUME;

Authentication & Credential Errors

Error Messages

User access disabled. Contact your local system administrator.

Credentials are invalid. Please check that the credentials you provided are in the correct format.

JWT token is invalid.

invalid credentials: credentials are not in a valid JSON format

Cause

Issues with authentication configuration.

Common reasons:

• user is disabled
• incorrect username/password
• invalid or expired key pair (JWT)
• malformed JSON credentials
• wrong authentication method

How to Fix

1. Check if user is active

SHOW USERS;

If disabled:

ALTER USER <user_name> SET DISABLED = FALSE;

2. Validate credentials format

• Ensure JSON is valid (no missing brackets/quotes)
• Ensure all required fields are present

3. Fix JWT / Key Pair Issues

If using key-based authentication:

• verify private key matches public key in Snowflake
• ensure key is not expired
• regenerate key if needed

4. Re-check authentication method

Ensure the method configured in Sifflet matches Snowflake setup:

• Username + Password
• Key Pair (JWT)

Metadata Access Errors (ACCOUNT_USAGE Views)

Error Messages

Table or view "SNOWFLAKE.ACCOUNT_USAGE.ACCESS_HISTORY" cannot be accessed.

Table or view "SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY" cannot be accessed.

Table or view "SNOWFLAKE.ACCOUNT_USAGE.OBJECT_DEPENDENCIES" cannot be accessed.

Table or view "SNOWFLAKE.ACCOUNT_USAGE.TABLES" cannot be accessed.

Table or view "SNOWFLAKE.ACCOUNT_USAGE.DYNAMIC_TABLE_REFRESH_HISTORY" cannot be accessed.

Table or view "SNOWFLAKE.ACCOUNT_USAGE.TAG_REFERENCES" cannot be accessed.

Cause

The role used by Sifflet does not have access to the SNOWFLAKE.ACCOUNT_USAGE schema.

These views are required for:

• query history (lineage & usage)
• table metadata
• dependency tracking
• tag propagation
• dynamic table monitoring

How to Fix

Grant access to the ACCOUNT_USAGE schema.

Step 1: Grant usage on database

GRANT USAGE ON DATABASE SNOWFLAKE TO ROLE <role_name>;

Step 2: Grant usage on schema

GRANT USAGE ON SCHEMA SNOWFLAKE.ACCOUNT_USAGE TO ROLE<role_name>;

Step 3: Grant access to views

GRANT SELECT ON ALL VIEWS IN SCHEMA SNOWFLAKE.ACCOUNT_USAGE TO ROLE<role_name>;

(Optional but recommended)

GRANT SELECT ON FUTURE VIEWS IN SCHEMA SNOWFLAKE.ACCOUNT_USAGE TO ROLE<role_name>;