954 questions
Hi @José Junior,
Thank you for reaching out to Microsoft Q&A forum!
Certainly! The error message “Parameter ‘Folder Path’ cannot be null or empty” typically occurs when a required parameter is missing or contains no value. Here are a couple of possible solutions:
Check the Flow Configuration:
- Verify that you’ve correctly configured the flow, especially the “Create file” action (if you’re using it). Ensure that the “Folder Path” parameter is set to a valid value.
- If you’re using OneDrive for Business, browse to the correct folder path in the “Folder Path” parameter1.
- If you’re using SharePoint, make sure the folder path exists and is accessible.
- If your flow is triggered by the addition of an item to a list, ensure that the necessary data (such as the UPN) is available before the flow executes. - [Avoid adding multiple items simultaneously in grid view, as SharePoint processes them immediately, potentially triggering the flow before all data is available](https://powerusers.microsoft.com/t5/General-Power-Automate/How-to-specify-Folder-Path-parameter-including-non-ascii/td-p/2150199)[2](https://powerusers.microsoft.com/t5/Building-Flows/Parameter-To-cannot-be-null-or-empty-but-it-s-not-empty/td-p/1504514). **User Error Handling:** - [Sometimes, simply deleting and re-adding an action can resolve unexpected issues in Power Automate](https://powerusers.microsoft.com/t5/Building-Flows/Parameter-To-cannot-be-null-or-empty-but-it-s-not-empty/td-p/1504514)[2](https://powerusers.microsoft.com/t5/Building-Flows/Parameter-To-cannot-be-null-or-empty-but-it-s-not-empty/td-p/1504514). - [Consider saving a new copy of the flow if other troubleshooting steps fail](https://powerusers.microsoft.com/t5/Building-Flows/Parameter-To-cannot-be-null-or-empty-but-it-s-not-empty/td-p/1504514)[2](https://powerusers.microsoft.com/t5/Building-Flows/Parameter-To-cannot-be-null-or-empty-but-it-s-not-empty/td-p/1504514).
- If you’re using OneDrive for Business, browse to the correct folder path in the “Folder Path” parameter1.
Remember to thoroughly review your flow configuration and data availability to pinpoint the cause of the error.