This problem again....
All my flows are failing due to "Body
I had a 100% success rate last week.
I know many people had this problem earlier but this was "solved" by creating the flow from a blank template, using Outlook instead of O365.
Any offical words?
How large was your file size? Did you try to run the flow with a small file? It seems that your file size exceeded maximum value.
What connection were you using? Outlook.com or Office 365 outlook?
I'm using the same files and sizes that worked flawlessly last week.
They are in a range of 3MB to 20MB.
I'm currently using a flow setup against Outlook due to the fact that O365 results in other type of errors - described in multiple topics by other users on this forum.
Monday again and the flow failed. Same error.
Last week I deleted all emails in the inbox and the flow was successful for the entire week.
Today I tried the same trick and it seems to work.
If the flow fail it seem to get stuck in a loop - trying to execute the same action over and over again. Next trigger will simply be ignored. I have a theory that the inbox size with multiple unread emails might be the cause of this.
Monday again, new fail.
This time, a new error! 😄
Every single Monday around 02-03 CET.
Whats the flow Id? We should get someone to take a look at what is happening.
The earlier error seems to be because the content is bigger. And it could have happened because of a mismatch in the config between the connectors and the flow engine.
Monday again which equals errors....
Can't get my head around this.
This time the flow seem to have gone corrupt. Can't reset it or make any changes:
"Could not find flow '513fab3c-0b4a-4463-a6e8-a346d2f3d709'."
Anyone else experiencing these issues?
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
Many congratulations to the Season 1 2021 Flownaut Crew!
ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.