Skip to main content

Relational Assets Builder
App

Resolve common issues when configuring or running the Relational Assets Builder app. This guide covers errors raised during term cache pre-processing and the steps to recover.

Import fails with "Term found with no anchor"​

danger

The Relational Assets Builder workflow fails during term cache pre-processing with IllegalStateException: Term found with no anchor.

Cause​

The error is raised when the workflow's term cache encounters an archived glossary term that no longer has a parent anchor (the glossary it belongs to). These orphaned terms are typically left behind when a glossary category is deleted while child terms underneath it still exist in an archived (soft-deleted) state. Because the archived terms remain in the system without a valid anchor, the workflow can't resolve their identity during cache pre-processing and aborts the import.

Solution​

The orphaned archived terms must be hard-deleted before the workflow can complete. Hard-deletion isn't available from the Atlan UI, so the cleanup has to be performed by Atlan support.

  1. Open a support request through Atlan support and reference the failing Relational Assets Builder workflow run, including the workflow name and the run ID where the error appears.
  2. Atlan support identifies the archived glossary terms that have no anchor and hard-deletes them from the tenant.
  3. Once the cleanup completes, re-run the Relational Assets Builder workflow. Term cache pre-processing can now succeed and the import can proceed normally.

Prevention​

To avoid orphaned archived terms in the future, purge child terms from a category before deleting the category itself. When the child terms are removed first, no archived descendants are left behind to lose their anchor when the parent is deleted.

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

See also​