So after abandoning our powerapp deployment in december last year due to the complete lack of stability of the service we decided to give it another shot.
1st time of using the service again and guess what.. a failure..
Converting 4 x documents from a docx to pdf using onedrive for business, 2 processed, the next one..
<h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.
Come on microsoft, this is meant to be business grade, not failing and wasting our time. If you have a problem then keep the flow running until its resolved so that completes as expected as now we have data loss which is unnaceptable.
Solved! Go to Solution.
so i reached out to my support team and this is what i was told should be able to help you.
This one's a known issue that arises when the Connection between PowerApps and Flows gets busted. Please delete the Flow as a DataSource and re-add it. Here's a similar Forum Post that will help
https://powerusers.microsoft.com/t5/General-Discussion/flow-launched-from-powerapps-error/m-p/43399
Hi @ Delid4ve,
Do you want to convert the .docx file to .pdf file using onedrive for business?
I have a .docx file in onedrive for business as screenshots below:
To convert the .docx file to .pdf file, you could create a flow as screenshots below:
The flow would run successfully as below:
And the .pdf file would be created in onedrive for business as screenshots below:
Regards,
Alice Zhang
Hey there!
Really sorry to hear about your data loss š - That sucks and its totally not acceptable.
Is there any way we can be of help now, on the back end of all of that?
Please do let me know.
Thanks!
Having the same issue. We attempted recreating the Flow, but still experiencing issues with the Convert File and Convert File from path functions that were previously working (HTML to PDF).
Hi jsarnold,
I have heard this same complaint from one other over the weekend.
Is the issue persisting? Please let me know and if so, i will alert engineering.
Thank you for following up. Stil having trouble, although the priblem has changed. I think the issue may be due to the fact I was passing HTML, instead of passing the table and using Flow's Data Operations to construct the HTML.
The beta app/flow work flawlessly for the first few days. When the issues first arose, it happened during the Convert File step, and the Error Details: HTML
Then the problemed evolved to:
Error Details: Unable to process template language expressions in action 'Create_file' inputs at line '1' and column '1761': 'The template language expression 'triggerBody()['Createfile_FileContent']' cannot be evaluated because property 'Createfile_FileContent' doesn't exist, available properties are 'Createfile_FileName, Sendanemail_To'. Please see https://aka.ms/logicexpressions for usage details.'.
Could be a long shot though.
Hi
We are also experiencing issues with flows that were working last week.
And this is the step error.
Whats actually acceptable ?
Thanks
So i spoke to the team today, this convert file action got messed up and theyre working to fix it now.
Very sorry for the inconvenience this might have caused. I will update when i have word that it is fixed.
This is happening across multiple functions:
The same error seems to be impacting all flows that are called from PowerApps.
I'm having the same issues with ALL my flows. Very frustrating
All your flows are failing?
Any of them that have to do with Send email.
Now I can't even select Email as an option. I'm getting an error the says Failed to fetch.
Have you tried deleting your email connection and remaking it?
When I try an add email back it says failed to fetch email. See screen shot is my last post.
Now I can't even get into my flow. I keep getting an error message the says something went wrong Refrech my page but the error never goes away. Screen shot included.
Can you click the gear in the top right corner of your screen and go to connections and try to delete/remake there?
It said it worked but I haven't recieved any emails.
User | Count |
---|---|
35 | |
15 | |
14 | |
13 | |
9 |
User | Count |
---|---|
42 | |
30 | |
26 | |
14 | |
12 |