Skip to main content

Troubleshooting Coalesce connectivity Private Preview

Common Coalesce connector issues and how to resolve them. If none of the symptoms below match, contact Atlan support with the crawl workflow ID.

Snowflake table shows no Coalesce panel or attributes​

Cause​

The Snowflake connector hasn't crawled the target table yet, or the most recent Coalesce crawl ran before Snowflake did—in both cases, the Coalesce enrichment has no Snowflake asset to attach to.

Solution​

  1. Confirm the Snowflake connector is installed and has crawled successfully.
  2. Open the affected table in Atlan and confirm it carries standard Snowflake metadata (column list, sample preview, etc.). If not, re-crawl Snowflake first.
  3. Re-crawl Coalesce. The enrichment attaches to the existing Snowflake asset.

Some nodes have status, others appear blank​

Cause​

Atlan surfaces status only from runs within the configured lookback window (7 days by default). Nodes not touched within that window, never run at all, or that are Source nodes (which don't have run state) appear blank.

Solution​

  1. In Coalesce, confirm the date of the most recent run that included the blank node.
  2. If the last run was more than 7 days ago, either trigger a fresh Coalesce run for that node, or contact your Atlan team to extend the lookback window.
  3. If the node is a Source, this is expected. Source nodes don't carry run state.

Run timestamp appears outdated after successful crawl​

Cause​

The Atlan crawl fired while a Coalesce job was still in progress. The in-progress run is skipped—the connector uses the previous completed run's timestamp until the next crawl.

Solution​

  1. Check when the most recent Coalesce job completed.
  2. Re-schedule the Atlan crawl to fire at least a few minutes after the Coalesce job completes. See Rate limits and scheduling for timing guidance.
  3. Manually re-run the Atlan crawl. The updated timestamp appears.

Crawl is slow​

Cause​

For large workspaces, the connector fetches per-node results serially—one API call per walked run per environment. Total crawl time scales with workspace size.

Solution​

  • Reduce crawl frequency to once every 4–6 hours for large workspaces.
  • Confirm with your Coalesce account team that your API rate-limit headroom is sufficient. Throttling on the Coalesce side adds backoff delay to every crawl.
  • Use include/exclude filters to restrict the crawl to only the projects and environments you need.

Rate limit errors in crawl logs​

Cause​

The connector's API call rate exceeded your Coalesce account's rate-limit threshold. Atlan retries with exponential backoff, so the crawl completes but runs noticeably slower when 429s are frequent.

Solution​

  1. Contact your Coalesce account team to confirm your current rate-limit threshold.
  2. Request a threshold uplift if your workspace size justifies it (typically workspaces with thousands of nodes).
  3. As a short-term fix, reduce the Atlan crawl frequency—for example, from hourly to every 4 hours—so the crawl has more time to complete within the rate limit.

Lineage edges between Coalesce and Snowflake are missing​

Cause​

Lineage requires both a Snowflake target table in Atlan and a valid sourceMapping on the Coalesce node. If either is missing, no lineage edge is created.

Solution​

  1. Confirm Snowflake has crawled the target schema.
  2. In Coalesce, open the node and confirm its source mapping references valid upstream nodes. Nodes with missing or incorrectly configured source mappings don't produce lineage edges.
  3. Re-crawl Coalesce.

Announcement banner missing on failed Coalesce node​

Cause​

Banners are written during the Coalesce crawl. If the crawl ran while the Coalesce job was still in progress (in-progress runs are skipped), or the Snowflake target table doesn't exist in Atlan yet, the banner can't be written.

Solution​

  1. Confirm the failed run has completed in Coalesce (in-progress runs are skipped).
  2. Re-run the Atlan crawl after the failed run finishes.
  3. Confirm the underlying Snowflake table exists in Atlan. Banners are written to Snowflake assets—the target must exist.

See also​

Need help​

If you need assistance after trying these steps, contact Atlan Support.