How to fix intermittent error in Azure Logic App. Error creating a file - Bad Request.
"status": 400,
"message": "The requested action could not be completed. Check your request parameters to make sure the path '\\\\scribe02\\DataBasics\\Azure\\Data_Files/wbsassignment.txt' exists on your file system.\r\nclientRequestId: 20475240-fede-4d58-b1ca-217bfe529887",
"error": {
"message": "The requested action could not be completed. Check your request parameters to make sure the path '\\\\scribe02\\DataBasics\\Azure\\Data_Files/wbsassignment.txt' exists on your file system."
Azure Logic Apps
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-17T04:44:00.4233333+00:00 @Robert K. Noebel Thanks for posting your question in Microsoft Q&A, apologize for any inconvenience caused on this.
Could you please share more insights on this to understand and assist you better.
- What are the actions involved in your logic apps?
- What exactly your logic apps does? and in which action you are seeing the above error message ?
- Can you check whether the file system path that is mentioned in the error message is present in your file system or not? also check whether you have access to create the file.
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-18T05:28:32.87+00:00 @Robert K. Noebel Following up to see if you have a chance to check the previous response and help us with the requested information to check and assist you further.
-
Robert K. Noebel 0 Reputation points
2024-09-18T13:07:20.3666667+00:00 GM Venkatesh!
The Logic App runs a SQL query (sproc) to generate data and the data is put into tab, delimited format and creates a .text file. Directory structure is good. Sometimes it works, sometimes it doesn't. If it fails, it restarts and trys a second time. Most of the time it succeeds the second time.
"status": 400, "message": "The requested action could not be completed. Check your request parameters to make sure the path '\\\\scribe02\\DataBasics\\Azure\\Data_Files/wbsassignment.txt' exists on your file system.\r\nclientRequestId: 2d35539a-3271-47cb-b599-e13d34b83956", "error": { "message": "The requested action could not be completed. Check your request parameters to make sure the path '\\\\scribe02\\DataBasics\\Azure\\Data_Files/wbsassignment.txt' exists on your file system." }, "source": "filesystem-cus.azconn-cus-001.p.azurewebsites.net" }
Not sure why the wonky fwd slash is there sometimes. Should be Data Files\wbsassignment.txt.
Thanks!
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-19T08:15:32.2833333+00:00 @Robert K. Noebel Thanks for sharing more details.
- I believe this file path in your workflow is dynamic and it getting created by one of the actions in workflow Could you please check the format in that has been using in that action.
- Also, as you mentioned that some this is working fine, can you check review & compare the run histories of succeeded and failed run to know better.
- If your logic app workflow has foreach loop and you are running in parallelism I would suggest you run it sequential instead of parallel.
-
Robert K. Noebel 0 Reputation points
2024-09-19T12:58:43.2333333+00:00 GM Venkatesh!
Run history:
Create file (where the error occurs). I go back and forth adding a '' to the directory, i.e. \Azure\Data_Files. Errors still occur intermittently.
No 'For each loops' in the logic app. Looks to be very sequential.
Any other suggestions? I have ten other logic apps doing the same thing as this one. This logic app, however, creates the largest file and takes the longest to run. All of the other logic apps use the same directory and same structure. The other logic apps simply use a different sproc and create a different .txt file.
Thanks!
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-23T14:19:41.59+00:00 @Robert K. Noebel Thanks for your response and sharing more details.
This needs one-on-one support or might need to engage the engineering team for deeper troubleshooting the issue. I would suggest you raise a support ticket to investigate further.
I have reached out to your over private message if you are facing any issue while raising the support case, please do share the requested information to assist you further.
-
Robert K. Noebel 0 Reputation points
2024-09-23T16:21:01.4966667+00:00 Hey Venkatesh,
I stand corrected by our developer. There is a loop in logic app (different than all others due to the size of the file created). I believe there were other issues before creating a loop, so we resolved one issue and created another.
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-25T04:25:31.0133333+00:00 @Robert K. Noebel Thanks for your response and glad to know that your problem was resolved post creating the new logic app.
-
Robert K. Noebel 0 Reputation points
2024-09-25T13:18:27.0433333+00:00 Sorry, I was misunderstood. I was saying before this file creation issue this logic app was having issues 'exceeding buffer'. That's when our developer created a loop. Then our file creation issues started.
You stated something earlier about loops. The question my developer has for you is if you don't do a loop, how do you process large files that exceed buffer? Thanks!!
-
VenkateshDodda-MSFT 20,536 Reputation points • Microsoft Employee
2024-09-27T05:38:01.1566667+00:00 @Robert K. Noebel As mentioned earlier I suggest you to raise a support ticket as this need on-on-one support to investigate or assist you further,
Sign in to comment