This Configuration Issue appears when Salto detects an element with a reference to another, non existing element.
What triggers this issue?
There are 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 Environment Settings -> Application Connections view
Salto was forbidden from accessing this element, due to some permission issue
Learn more about this problem in this article
Salto 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 application itself; for example, a Jira automation with a reference to a field or project which no longer exist
To fix this, go to the application itself and fix the broken reference