Power Platform Community Forum Thread Details

I currently have three flows that work together to do one thing:
The goal of the flows is: when an email arrives with a certain title containing a zip file, extract that file and save the .csv it contains to a sharepoint folder, overwriting previous versions. Its broken into three flows, it could probably be remade into one but I had trouble with that.

The first flow saves the zip from the email in a staging folder, it looks like this and it tends to work well:

The next flow takes that zip, checks to see if it is a ".zip" and unzips it into the same staging folder, then deletes the .zip. It tends to work well also. Looks like this:

The third flow looks for newly created .csv's (should have happened when it was unzipped), makes sure they're csv's, and saves them with a certain name ("irb_biweekly_extract.csv") in the final destination folder, looks like this:

Here's the problem: sometimes the final flow errors because it says the file already exists in the destination folder. That's true, I know it already exists, I want it to have the same file name. I could delete it with an earlier step, but then the flow fails if the file doesnt exist for some reason (previous flow, etc). Also, I swear the flow has worked previously and overwritten the file:

Sometimes it just decides not to.

Also, sometimes the final flow doesn't notice a new csv was created and instead only notices a new file was created when the .zip was made. So because its a zip, the final pictured condition (that checks for .csv) says false and no file is created.

It's probably best to have a singular flow that goes straight from email to csv in the final folder, but when I was building this I noticed it seems like someone else ran into a similar problem and had to make separate flows:
https://community.powerplatform.com/forums/thread/details/?threadid=710d2461-1f8c-4686-8d90-d47e98f10b2e

Any ideas? Either to make a singular flow or clean up some of the problems?

Categories:

Building flows