topic Re: Asset Bundle Validation Not Completing – Stuck on files_to_sync in Data Engineering

Asset Bundle Validation Not Completing – Stuck on files_to_sync

Davila — Wed, 25 Jun 2025 21:42:53 GMT

I have a Databricks asset bundle with the following structure:

bundle: name: <some value here> uuid: <some value here> include: - resources/*.yml variables: catalog_bronze: {} catalog_silver: {} user_name: {} targets: dev: mode: development default: true git: branch: dev variables: catalog_bronze: <some value here> catalog_silver: <some value here> user_name: <some value here> workspace: host: <some value here> root_path: <some value here> run_as: user_name: ${var.user_name} prod: mode: production git: branch: main workspace: host: <some value here> root_path: <some value here> variables: catalog_bronze: bronze_rock_prd catalog_silver: silver_rock_prd user_name: <some value here>

When I run the following command:

databricks bundle validate --profile dev --target dev --debug

The validation process takes a very long time, even though my bundle contains very few files.

The last log message I get is:

17:56:13 Debug: Path <my root path> has type directory (ID: <some value> ) pid=17736 mutator=validate:files_to_sync

Has anyone faced this issue? Any ideas on how to speed up the validation or troubleshoot what’s causing the delay?

Re: Asset Bundle Validation Not Completing – Stuck on files_to_sync

Renu_ — Thu, 26 Jun 2025 14:13:24 GMT

Hi @Davila, Validation can be slow if your bundle root includes a large number of files. However, since your bundle contains only a few files, the delay may be due to the root_path pointing to a broader directory structure in the Databricks workspace.

It’s also a good idea to review your .gitignore file, if it’s not properly configured, the CLI might scan unnecessary files. Updating it to exclude irrelevant paths can help improve validation performance.

Re: Asset Bundle Validation Not Completing – Stuck on files_to_sync

Davila — Thu, 26 Jun 2025 16:43:55 GMT

Hi @Renu_ , thanks for the suggestion! After reviewing my root folder, the validation started working properly. My .gitignore was already well configured, and I noticed that after the first run, the validation process runs much faster. Looks like the initial delay was related to the broader directory structure, just as you mentioned.