The power flow's logic app flow template was invalid.The power flow's logic app flow template was invalid.

[RizwanShah909]

For the selected file trigger, I am having the following issues, can anyone suggest the solution?

The power flow's logic app flow template was invalid. The 'type' property of template trigger 'manual' at line '1' and column '61435' has the value 'Manual' which is deprecated in schema version '2016-04-01-preview' and onwards.

[v-jefferni]

Hi @RizwanShah909 ,

Could you lease share the trigger settings of your flow in screenshots?

Best regards,

[THenchoz]

Hello,

I'm also encountering this issue with the same trigger ('For a selected file' from SharePoint), as below.

I've tried removing the trigger and add a new one, but the issue remained. As ask, here are the settings of the trigger:

 

Thanks for your help

Best regards

[RizwanShah909]

My trigger settings are same. Workflow is running fine but error remains. created a ticket to Microsoft support but they don't have any answers. 
In other cases whenever I create a new workflow specifically by using template for example: page approval out of the box workflow, it works fine but i get the same error.

[RizwanShah909]

I have not tried it yet myself, but perhaps can help solve the problem.

https://powerusers.microsoft.com/t5/General-Power-Automate/The-power-flow-s-logic-app-flow-template-...

Only issue is, even in my new flows i am getting this error. 

[KarlInOz1]

I started seeing this issue today as well. Have not changed anything in the flow for a week. When I created it it was fine, no errors. Went back today to edit it and I get this error at the top.

[KarlInOz1]

OK, so after hours of testing by eliminating blocks in my troublesome flow, I have found how to replicate the issue reliably and simply, in my account anyway.

Build a flow with the trigger For a selected item. Add a Switch action. In the Switch action create a manual array in the On field. Add a Case. It may even happen under Default, I haven't tested that. In the case add a compose action with anything in it, in fact, this seems to happen with any action in the case. Save the flow, back out of it then choose to edit it and Voila! you get the error. That's a brand new flow and you get the error.

[KarlInOz1]

And actually I see I have an error in the On field. So, replace that with a string expression 

string('Cat')

 and save that. You get the same result.

[KarlInOz1]

I raised a support ticket with MS and the response is:

After consulting with our team, it appears that the problem you raised is one that persists with our service.

However, please be assured that our product team is actively working to resolve it and will address the issue internally. We anticipate that a solution will be implemented soon and made available in the near future.

---

[THenchoz]

@KarlInOz1 thanks you for your research and the MS ticket !

[Anonymous]

Hi all, I came across this issue today when a user reported that the button on my sharepoint list that is supposed to run a flow did nothing (come on MS can we not get some kind of message to the user when the flow template is broken?)

I opened the flow in question and got the mentioned red banner. I opened my trigger settings, closed them, and saved the flow and the error has gone. Will update you all once the user tries to run it again.

[Anonymous]

So,

after I took those steps, the Flow is working again

HTH

[RizwanShah909]

Dear all, 
Tenant had recently received an update, after that I went back to 5 different workflows using the same trigger, 
I opened the workflow in edit mode, refresh and reset the workflow. the error disappeared. 
The error was basically with the template itself provided by the Microsoft (which was outdated), so it was just the matter of updating it and error was removed. 

So wait for the update of your tenant and update and refresh your workflows, save/publish again and it will be error free provided if you don't have any other error. Microsoft is rolling out fix for this issue. 

if you like this answer, please "Accept as Solution" 🙂

Regards,

Rizwan 

[Anonymous]

Hi Rizwan. Sounds similar to my approach. What do you mean by "reset" the flow.

[RizwanShah909]

Reset means: "just Save". also check if any value gone missing from the workflow. For example in my case ID of the metadata action was missing and I reset it again. 

however its all about update from the Microsoft. 

Regards,

Rizwan

[rsorourke02]

I started having the same issue with my flow. Very frustrating in that the trigger condition to limit to file modification instead of creation worked just fine on Tuesday, then Thursday started generating this error. Rebuilt the flow from scratch and still got the same error. Thought I was crazy til I found this thread.

Looking forward to MS fix, commenting so as to hopefully be notified of fix.

"The power flow's logic app flow template was invalid. The template condition expression <expression> at line '1' and column '4443' is not valid template language expression.