Connectors

Use Orchestration > Connectors to inspect and compare DaVinci connector instances.

Connector mappings are critical for flow migration because a copied or upgraded flow must bind to compatible destination connector instances.

Common Uses

• Review connector instances.
• Compare connector configuration across environments.
• Confirm destination connector readiness before migration.
• Troubleshoot Director dependency issues.

Basic Workflow

1. Select an Org Root.
2. Select a source environment.
3. Optionally select a destination environment.
4. Search for the connector instance.
5. Open or compare connector details where supported.

Compare Behavior

Connector comparison ignores volatile instance metadata where appropriate, such as environment-specific IDs and timestamps, so the comparison focuses on meaningful configuration.

Director Dependency Resolution

FlightIQ Director may ask you to resolve connector mappings before executing a migration.

Before choosing a mapping:

• Confirm the destination connector instance belongs to the intended service.
• Confirm credentials and environment-specific settings are correct.
• Avoid mapping to similarly named but functionally different connector instances.

Repository Use

Repository-safe connector behavior may be narrower than live PingOne behavior. When repository sources are used, FlightIQ may limit connector handling to supported repository-safe connector types.

Troubleshooting

If connectors do not appear, confirm:

• Source environment is selected.
• Worker app has DaVinci read access.
• Search and filters are cleared.
• Destination connector instances exist before running a migration that depends on them.