This fetch error appears when trying to fetch an application connection, but the security application prevents Tulip from getting some type of data.

When fetching an application connection, Tulip sends API requests to the security application to get all required elements.

To authenticate with the security application, Tulip uses the credentials supplied by the application connection creator.

The "Tulip could not access the resource" fetch error occurs when Tulip tries to get some element, but is prevented by the security application from doing so (and the application returns a "403 Forbidden" or “401 Unauthorized” error). This usually happens because the supplied credentials did not have sufficient permissions to access a specific data type, but can also happen when the security application has specific features disabled.

Tulip can only get elements which are allowed for the supplied user credentials.

To avoid this error, make sure that the application connection's credentials belong to a user which has permissions to access the missing elements.

You can either add permissions to the user in the security application itself, or change the Tulip application connection credentials to a user which has sufficient permissions to access all data.

To change the credentials Tulip uses, go to the Applicaiton page and click on the 'settings' button of the relevant application connection.

Then navigate to the 'Credentials' section and edit the shared credentials of the application connection.

Alternatively, you can change your application connection configuration to exclude this type of resource when fetching. Learn more about editing your app connection fetch configuration here.

​