Preflight checks for Databricks
Before [running the Databricks crawler](/apps/connectors/data-warehouses/databricks/how-tos/crawl-databricks), you can run [preflight checks](/product/co.
Before running the Databricks crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks will be completed:
JDBC
Schemas
✅ Check successful
❌ Check failed for $missingObjectName
System tables
AI/BI dashboards
Runs only when Import AI/BI Dashboards is turned on. Atlan probes the Databricks Lakeview API to confirm it's reachable and the service account is authorized.
✅ AI/BI dashboards (Lakeview) are reachable. Note: LIST is ACL-filtered, so this proves reachability only, not full coverage of every dashboard (check dashboard folder visibility if some dashboards are missing).
❌ User doesn't have permission to access AI/BI dashboards (Lakeview), please check dashboard folder access before enabling dashboard ingestion.
A successful check confirms the service account can reach the API—not that it can see every dashboard. Because the Lakeview API filters results by access control, dashboards the account can't view are skipped during the crawl without an error. See Why are some dashboards missing after crawling?
Rest API (Unity Catalog)
The REST API extraction method for crawling Databricks metadata is deprecated. Use the system tables extraction method instead. The preflight checks below apply only to the deprecated REST API method.
User login/UC enabled
✅ Check successful
❌ Source returned error
For example: {"error_code":"403","message":"Invalid access token."}
Catalog
✅ Check successful
❌ Check failed for $missingObjectName catalog
Databricks lineage and usage (miner)
Once you have crawled assets from Databricks, you can extract lineage and usage and popularity metrics.
Login
✅ Check successful
❌ Check failed
For example: {"error_code":"403","message":"Invalid access token."}
Lineage API (Deprecated)
The REST API lineage extraction method is deprecated. Use the system tables method instead.
✅ Check successful. Lineage API is enabled.
❌ Check failed
For example: Lineage is not enabled for this Databricks account: 47258391-b3c8-4ff9-a0d9-5afc02443806
Query history API endpoint check (Deprecated)
✅ Check successful
❌ Check failed