Queue FTP Copying Files Send Email Notification

Carol Grant

I'm tired of getting multiple status email updates from Queue saying Did Not Complete then a Completed one. Sometimes I can't tell if it did complete or not. So I've decided to add my email to the FTP Copy flows that I have. This works well but many of my Queues have multiple exports so I end up getting 4 emails for each file for some of them.

I'm stuck on how to send only one email saying it's done copying them. I've tried an Apply to each and appending the file name to an array but I can't get that into the body of the email.

Any ideas- I've googled it but nothing concrete. Many things about attaching multiple files to the email but nothing for copying files and sending only one email.

Do I need to list the files in the folder and use that?

The only downside is I won't know if it doesn't run because this only works when a file is created. I'll have to deal with that issue later.

Here's what the flow currently looks like.

Alex Wong

@Carol Grant
one of the main reason why I do not use RE:Queue SFTP anymore. My new contract that just got signed removed RE:Queue, since I can make do with Query API for everything I need.

Since you are using the trigger for when a file is modified, your flow trigger once per file, there is no way for you to only get one email like this, each flow doesn't “share” info with one other, unless you create a “place” where the info can be shared.

Meaning, you can create a sharepoint list, or excel, where you are recording each RE:Queue's file name, and a last modified date. at the end of your flow, you will update the last modified date on the sp list/excel by the filename matching. No sending email.

Have another scheduled flow that runs at a time that you believe all the RE:Queue should have finished, and check all the last modified date to see if the file's last modified date falls within what is expected, if not, then send email showing the files that didn't have expected last modified date.

Carol Grant

@Alex Wong- thanks Alex, I was hoping there was a better solution. That's too bad but I understand what you mean. I'll think about implementing the last modified date and having a separate flow to check that. Thank you

Alex Wong

@Carol Grant
I would encourage you to spend some time to think about the RE:Queue that you are currently doing and modify from that to Query API.

If you need help converting something to Query API, post here, I can try to help