Troubleshoot Databricks profiler

Known issues with connector_info_id synchronization

HTTP 422 "connector_info_id not found — call POST /connector-info first", even though the connector already exists and works elsewhere. This can occur after an incomplete environment reset, where only part of the deployment data was cleared.

Workaround: When resetting a deployment, reset all deployment data in a single operation. Do not reset individual components separately, and always use a connector ID created in the current environment rather than one reused from a previous or different environment.