Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content
Qlik Resources

Troubleshooting - Lineage messages

You may encounter one or more of the following messages when working with lineage and impact analysis in Qlik Cloud. This table is intended to provide more context and guidance to help you understand and resolve common issues around lineage.

Lineage message Explanation
No lineage data available This message means that the node is not found in lineage data. This can happen if an associated app has not been reloaded, or an associated data task has not been prepared.
Resource has been deleted or never existed. The ID of the resource is wrong or it has been deleted.
Resource is not available because app has not been reloaded or lineage could not be found.

Possible causes:

  • An app related to this lineage has not been reloaded since the lineage feature was introduced .

  • There was an error generating the lineage.

  • A data task related to this lineage has not been prepared since the lineage feature was introduced in Qlik Talend Data Integration.

Examples:

  • An app that does not write any data.

  • A dataset that is not being read.
Internal error There was an internal error involving services that provide lineage.
No impacted resources exist for the selected base node. The base node does not have any output registered that would generate lineage. An examples of this is an app or data task that does not write any data, or it produces a dataset that is not being read.
No upstream lineage data available The base node does not read any data and is therefore not dependent on any nodes.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here