When fetching your app connection, Tulip may encounter issues that prevent the fetch from completing successfully. These issues are listed in the "Problems" tab on your app connection page. To review your configuration issues, click the exclamation mark icon on the relevant application connection card.
In this screen, you can view all configuration issues, and get more details about each one by clicking on them. If these issues affect a specific configuration element, clicking on them will also show you the affected element.
We recommend users review and fix Configuration Issues early on, as some of them may prevent successful deployments or impact your security posture assessment.
Common configuration issues
The common issues users encounter are:
Credential issues
Tulip could not access the application configuration, as the supplied credentials were incorrect or expired. Make sure your credentials are set correctly by following these instructions
Permission and access problems
Tulip could not access some parts of the configuration, due to permission issues. This usually means that the user credentials have missing permissions configured on the security application side; fix those and try fetching again.
ID collisions
This issue indicates that multiple application configuration elements were assigned the same Tulip Element ID, which prevented them from being fetched. Read more about this problem and solutions in this article.
Missing References
This issue indicates that an element contains a reference to another element, which does not exist in the Tulip app connection. This can be a result of an ID collision which prevented an element from being fetched, or simply a broken reference in the security application itself (for example, a policy or automation which still points to a field deleted in the past).
Invalid Configuration
This issue means that some invalid configuration was made in your app connection configuration file. Access the file by clicking this issue and fix the problem.
There are additional, less common issues that users may encounter. Follow the instructions on the issue itself to understand and fix it.