cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Bourmatnov
Frequent Visitor

Successful 'Create File' FTP transfer causes improper exception

I have used the standard trigger template to build a OneDrive to FTPS  transfer.  This flow is supposed to be triggered by One Drive folder having a file dropped in it and create the new file over in FTP server land.  I have two issues. 

 

1) Dropping a file in the source folder being monitored does not fire the trigger. (I can however "test" it using the forced mode available in edit screen)

 

2) When the file is successfully transferred PA reports the following failure:

"The requested action could not be completed as the specified resource (file/folder) does not exist or is busy."

I suspect this might be cause by the FTP Server picking up and renaming the new file right away for processing.  If so is there a way to work around the PA exception without having PA reporting the flow as a failure?

 

Thanks

 

2 REPLIES 2
alrez
Community Support
Community Support

Hi,

 

Without troubleshooting and looking at the flow I don't think its possible to figure out what is going on with the trigger of the flow, this will probably need to be looked at by Microsoft Support. I'll include a link below; on creating a case with them.

 

For the second issue, it depends on where the error is being thrown at. If PA is changing your file name it should have meta data to track that, that we just need to get adjusted to correctly adjust the pathing. However I would need to see the flow, you can also always bring up this also on the Microsoft Support request.

 

If you would like to create a ticket with Microsoft Customer Support here is a link on how to do so: https://docs.microsoft.com/en-us/power-platform/admin/get-help-support

 

Regards,

 

Alex

 

-------

 

Community Support Team _ Alex Rezac
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Thanks Alex,

 

Regarding the second issue, I was able to catch the exception using a switch step (with run after exception turned on) where each case leads to a step for managing a given error code and wraps up with a terminate step. I allow the 404 Not Found error to be considered a success and any other exception triggers an email warning (except 200 of course).

 

Paul

 

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Community Calls Conversations

Community Calls Conversations

A great place where you can stay up to date with community calls and interact with the speakers.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (5,746)