If you're exploring an application connection and can't find the element you're looking for, it could be due to one of the following reasons:
Outdated Application Data: Your application connections may not have been recently fetched, so Tulip might be unaware of recent configuration changes. Fetch your source or destination application to update Tulip with the latest changes.
Adapter Configuration: Your adapter may not be set to fetch the element type you're searching for. Refer to the adapter-specific documentation to learn how to include additional types during fetch.
ID Collision: The element may have been omitted due to a Tulip ID collision.