Hi  @Shivani_Komma99 

What you're describing is consistent with a known behavior in Unity Catalog-enabled workspaces.

The most likely explanation is related to cluster access mode:

• Compute resources configured with dedicated access mode have full access to DBFS, including all files in the DBFS root and mounted data. This is probably why your jobs are still running successfully.

• In standard access mode, to interact with files directly using DBFS, users must have ANY FILE permissions explicitly granted. Without it, the folder may appear empty in the UI even though the files are physically there.

Also worth noting: both DBFS root and DBFS mounts are deprecated and not recommended by Databricks. New accounts are provisioned without access to these features.

A few questions to better understand your setup:

1. What cluster access mode are your jobs running on — dedicated (single-user) or standard (shared)?

2. How are you navigating to the DBFS path — via the UI file browser, dbutils.fs.ls(), or the CLI?

3. Is Unity Catalog enabled in your workspace?

This will help us point you to the right solution for uploading the new file safely. Thanks!