Troubleshoot

SPAN Identity Graph — Troubleshooting Guide

This guide covers common issues encountered during installation and execution of SPAN Identity Graph.

If an issue persists, contact:

support@span-data.com


1. Installation Issues

Issue: Installation Fails

Possible Causes

  • Insufficient privileges

  • Required privileges not approved during installation

  • Marketplace listing not fully published

  • Application package not externally distributed

Resolution

  • Ensure you have a role with application installation privileges

  • Confirm all requested privileges are approved

  • Contact your Snowflake administrator if necessary

  • Verify the listing is published and available in your region


2. Privilege Errors

SPAN operates under Snowflake RBAC. Most runtime errors are privilege-related.


Issue: "Insufficient privileges to access table"

Cause

The active role does not have SELECT permission on the selected source table.

Resolution

Grant the role:

Ensure the role also has:

  • USAGE on database

  • USAGE on schema


Issue: "Cannot create table in schema"

Cause The role does not have CREATE TABLE permission in the output schema.

Resolution

3. Warehouse Issues

Issue: Identity Graph fails to start

Possible Causes

  • Warehouse is suspended

  • Warehouse size too small for dataset

Resolution

  • Resume warehouse

  • Increase warehouse size if processing large datasets

SPAN consumes compute only during execution.


4. Field Mapping Errors

Issue: Column not found

Cause Selected column does not exist in source table.

Resolution

  • Verify column names

  • Confirm correct database and schema selected

  • Refresh metadata if schema changed


Issue: Key column not unique

Cause The selected unique identifier column contains duplicate values.

Resolution

  • Choose a truly unique key

  • Or generate a surrogate key before running SPAN

Example:

5. Identity Graph Behavior

Issue: Too many records merged

Cause Blocking rules are too broad.

Resolution

  • Narrow matching rules

  • Remove low-precision rules

  • Re-run graph


Issue: Too few records merged

Cause Blocking rules are too strict.

Resolution

  • Add additional rule combinations

  • Include secondary identifiers (phone, address, etc.)


6. Output Table Issues

Issue: Output table already exists

Cause Table name conflict.

Resolution

  • Choose a new table name

  • Drop existing table manually if safe


Issue: Output table empty

Possible Causes

  • Source table empty

  • Blocking rules overly restrictive

  • Field mapping incorrect

Resolution

  • Validate source data

  • Check mapping configuration

  • Review blocking rules


7. Performance Questions

Issue: Graph processing is slow

Performance depends on:

  • Table size

  • Number of blocking rules

  • Warehouse size

Recommendations

  • Increase warehouse size

  • Reduce number of blocking rule combinations

  • Ensure source tables are properly clustered/indexed


8. Uninstall & Cleanup

Issue: Output tables remain after uninstall

This is expected behaviour.

SPAN removes application-managed objects. User-created output tables remain unless manually removed.


9. When to Contact Support

Contact support if:

  • Identity Graph fails without clear error message

  • Security or privilege behaviour seems incorrect

  • Upgrade issues occur

  • Unexpected object creation is observed

Include in your support request:

  • Snowflake account name

  • Role used

  • Error message

  • Screenshot (if applicable)

  • Approximate dataset size

Email: support@span-data.com

Last updated