Power Platform Community Forum Thread Details

We have created an automated Flow that does the following:

1. Check shared mailbox for email as it arrives - must have attachment

2. Each attachment that ends in .pdf is copied through "Create file" action, through a Data Connector to an SMB share.

3. If there was any attachment moved, move the original message out of the inbox and into a subfolder in the shared mailbox.

Outside of this Flow (not related): A third party app periodically polls the same SMB share, and moves any files OUT of the share. The end goal of our Flow is to feed this share the files for this third party app.

This Flow is working correctly up until the point of the "Create file" action. It even creates the file successfully. However, because the 3rd party app moves the file out of the share in a timing we cannot control, we are seeing a failure on the "Create file" action:

{

"status": 404,

"message": "There is no file with name 'invoice1.pdf' located in '[share]' on your file system. Verify the file exists or create it before trying to access it.\r\nclientRequestId: [request ID]",

"error": {

"message": "There is no file with name 'invoice1.pdf' located in '[share]' on your file system. Verify the file exists or create it before trying to access it."

"source": "filesystem-eus2.azconn-eus2-01.p.azurewebsites.net"

}

This causes the Flow to report failure and the rest of the logic to fail (aka moving the message into a subfolder).

If we move the file to a different SMB location (where the file does not get pulled out), it works successfully.

Is there anything we might do to let the Flow perform the "Copy file" action, but either skip or work around whatever validation is taking place that reports the failure? I was thinking of copying the file to a root location and then performing a move, but again, due to the third party app moving the file, I have a feeling any file action from Flow will end up failing a subsequent check that the file is there.

Categories:

Error handling