Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered

Reply
JohnAG
Frequent Visitor

ADF Data Flow Fails with "Path does not resolve to any file" — Dynamic Parameters via Trigger

Hi guys, 

I'm running into an issue with my Azure Data Factory pipeline triggered by a Blob event.

The trigger passes dynamic folderPath and fileName values into a parameterized dataset and mapping data flow.  

 

Everything works perfectly when I debug the pipeline manually or trigger the pipeline manually with the trigger and pass in the values for folderPath and fileName directly. However, when the pipeline is triggered automatically via the blob event, the data flow fails with the following error:

Error Message:
Job failed due to reason: at Source 'CSVsource': Path /financials/V02/Forecast/ForecastSampleV02.csv does not resolve to any file(s).
Please make sure the file/folder exists and is not hidden. At the same time, please ensure special character is not included in file/folder name, for example, name starting with _

 

  1. I've verified the blob file exists. 
  2. The trigger fires correctly and passes parameters 
  3. The path looks valid. 
  4. The dataset is parameterized correctly with @dataset().folderPath and @dataset().fileName

I've attached screenshots of:

🔵 00-Pipeline Trigger Configuration On Blob creation
🔵 01-Trigger Parameters
🔵 02-Pipeline Parameters
🔵 03-Data flow Parameters
🔵 04-Data flow Parameters without default value
🔵 05-Data flow CSVsource parameters
🔵 06-Data flow Source Dataset
🔵 07-Data flow Source dataset Parameters
🔵 08-Data flow Source Parameters
🔵 09-Parameters passed to the pipeline from the trigger
🔵 10-Data flow error message

 

Here are all the images

What could be causing the data flow to fail on file path resolution only when triggered, even though the exact same parameters succeed during manual debug runs? Could this be related to: 

  1. Extra slashes or encoding in trigger output?
  2. Misuse of @dataset().folderPath and fileName in the dataset?
  3. Limitations in how blob trigger outputs are parsed?

Any insights would be appreciated!

 

Thank you 

 

1 ACCEPTED SOLUTION
v-sathmakuri
Community Support
Community Support

Hi @JohnAG ,

 

Thank you for reaching out to Microsoft Fabric Community.

 

As this is microsoft fabrics forum, i would suggest raising a ticket is ADF forum https://techcommunity.microsoft.com/category/azuredatabases/discussions/azuredatafactory 

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 

Thank you!!

View solution in original post

1 REPLY 1
v-sathmakuri
Community Support
Community Support

Hi @JohnAG ,

 

Thank you for reaching out to Microsoft Fabric Community.

 

As this is microsoft fabrics forum, i would suggest raising a ticket is ADF forum https://techcommunity.microsoft.com/category/azuredatabases/discussions/azuredatafactory 

 

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

 

Thank you!!

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June FBC25 Carousel

Fabric Monthly Update - June 2025

Check out the June 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.