You’re offline. This is a read only version of the page.
Announcements
9
Context: I have a flow I've been using for a while that simply publishes a file from a SharePoint online location (for staging/backup) to a OneDrive, where my team can work on the file. I accomplish this with a manually-triggered SharePoint "Copy file" action. That's been working smoothly with no issues. Now I'm trying to add an email function so I can send my team an email automatically when the file has been published. I added a "Yes/No" input to my manual trigger to notify the team. I created a test flow for the email with my input to ensure that my flow would, in fact, send the email correctly and it was all good.
The Problem: When I added my "Yes/No" input to my "Copy file" flow and included a condition to send the email if my input = true. Now when I run my flow, the file updates fine when my input = false. However, when input = true, it seems to get stuck copying the file (before the condition in the flow). As of this writing, a flow that normally takes 9 seconds (max), is currently sitting at 40+ minutes.
The Flow: I have a picture of the flow attached, but here it is in text format:
Manual Trigger w/ Yes/No input --> SharePoint Copy file action (from SharePoint Online to OneDrive) --> Condition where input = true --> If yes --> send email. If no --> (no action).
I'm sure I'm missing something that's probably pretty simple, but I can't figure out why selecting the input as true will seemingly make my flow get stuck in the Copy file action.
I found a solution, though it seems to be more of a workaround than anything else. I split the "Copy file" and Condition-fed Email actions into parallel actions. So from my button trigger and Yes/No input, the flow will simultaneously perform the Copy file and (if selected) Email actions. I've run it a handful of times with the Yes/No action toggled both to be on and off. It hasn't given me any issues yet.
However, I do realize that this does not achieve the same thing, as I could have the file fail to copy for some reason, but still send out an email since they're run in parallel. Ideally, I'd like this to be a linear fix, so I'm still open to potential solutions.
Share
Report
All responses (
Answers (
