I have a simple flow that checks my Office 365 email and when it detects a certain subject line pattern it creates a file in Sharepoint using the associated attachement.
It is fine with the Flow Checker and runs with no errors - however no attachements are saved to SharePoint.
I have checked the Connections it is using and it has my identity with the organisation.
To try and identify where the issues is (not accessing the inbox or not able to create file in Sharepoint) I need to find a way to find out exactly what thye Flow is doing.
Anyone know how to create or find detailed information about what is happening within a flow?
First, take a look a one of your Flow runs - it will show you exactly what happened and allow you to see the values used in your Flow. To view the run, simply click on it.
Please post a screen shot of your Flow.
To view the run history:
(1) Go to My flows and (2) select your flow:
(3) Look at the 28 day run history. Click one of the run histories:
The flow run history is shown:
Click on one of the action headers to view the history of that action item:
Told you it was simple.
Ironically had a different version of this working fine for months, then I mistakely volunteered to be an Ofice 365 MFA early adopter, which broke my flows.
After much futile attempts to get those working with authenticating them, I got my Office 365 MFA switched off, started from scratch and found it still didn't work.
I have that - and AFAIK it indicates that it has created the files from the attchment.
It has definitely picked up the right attachment name
Have added the outputs for the above - which look right to my novice eye.
As suggested by @ekarim2020 the output does indicate that a file was created. Is it possible that your SharePoint view is filtered and does not show the new document?
Try doing a search in SharePoint for the document.
> Is it possible that your SharePoint view is filtered and does not show the new document?
That was not it - but it did lead me to do a search of the whole organisation.
I am ashamed to admit a silly error.
I had a similiarly named Sharepoint space (not used for a long time) which I had inadvertently used in the selection box for where to save files to.
In my rather lame defence the file path was very long and the name didn't fully appear in the selection field so I hadn't spotted it.
Can we all pretend that this never happened....?
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
Are you new to designing flows? What is your biggest struggle with Power Automate Designer? Help us make it more user friendly!