This Configuration Issue appears when Tulip detects an element with a reference to another, non-existing element.
What triggers this issue?
There are a few possible reasons why a reference might be unresolved:
Your fetch configuration excludes some items, including the referenced one
To fix this, change your fetch configuration from the Application settings->General->Edit Configuration File button
Tulip was forbidden from accessing this element, due to some permission issue
Learn more about this problem in this article
Tulip detected an ID collision which prevented some elements from being fetched
Learn more about this problem in this article
The reference is missing in the security application itself; for example, a workflow automation with a reference to a field or policy which no longer exists
To fix this, go to the application itself and fix the broken reference