If you're comparing app connections during a deployment and can't find the element you're looking for, it might be due to one of the following reasons:
Identical Elements or Outdated Application Data: The element may be identical in your source and destination applications, as Tulip only displays elements with differences during comparison. Additionally, if new elements have been added or existing ones updated but not yet fetched, Tulip may not reflect these changes. Fetch your source or destination applications to ensure Tulip is up to date with the latest configuration changes.
Adapter Configuration: Your adapter may not be configured to fetch the element type you're looking for. Refer to the adapter-specific documentation to learn how to include additional types when fetching applications.
ID Collision: The element might have been omitted due to a Tulip ID collision.