Flow save error, odd behavior

(0) Share

Report

Posted on by Community Power Pla...

A Flow which worked fine for weeks now continuiously in errors.

When trying to fix this problem I found out I can't even save the Flow properly anymore.

Sometimes the Flow can be saved, sometimes these errors are shown:

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

Definition contains invalid parameters.

Furthermore I found this text in a 'Update File properties' part:

I haven't added this text.

Please see this video for a demonstration:

https://youtu.be/bfi-rGNA3wY

Note: we didn't change anything on the Flow or SharePoint library to which it is connected.

I've tried to export and import the workflow bu the problem persists.

Also tried to change the 'manual' property which the first error refers and then import the Flow, but Flow won't import the Flow.

How can this Flow be fixed again?

Categories:

Using flows

I have the same question (0)

All responses (21)

Answers (0)

v-yamao-msft on at

Like (0)

Report

Hi @Anonymous,

How long has the flow been created? The error says that the value Manual is deprecated in schema version 2016-04-01 preview.

Please try to upgrade the schema to see if it will work. Please check this doc for more details:

https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-schema-2016-04-01#upgrade-your-schema

Please also try to recreate the flow to see if it will return the same error.

Could you share the detailed configuration in your flow? I will try to reproduce this issue on my side.

Best regards,

Mabel Mao

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hi Mabel,

The Flow was created in may this year (approximately 4 months ago).
Since this a Flow an not an logic app, there's no way for me to upgrade the schema.

I've other workflows which were created around the same time that still work normally.
When I try to export the current one and import again the problem persists.
When I upload old backups of the file (from may and from july) they also show this strange behaviour.

How do you want to receive the detailed configuration? I could send an export of the Flow.

Thanks,
Jean-Paul van den Bogert

Was this reply helpful? Yes No
v-yamao-msft on at

Like (1)

Report

Hi @Anonymous,

Thanks for updating.

Please share screenshots of what value you have specified for each field for each step. I will help reproduce this issue on my side.

Best regards,

Mabel Mao

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Hi Mabel,

here you go. The Flow is quite large, I want to emphasize that it worked just fine in the past.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hello @Anonymous !
Did you manage to solve this?
I have the same problem.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

Yes,
I solved it by deleting parts of the Flow and adding them manually again.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Thanks @Anonymous
Are there any specific parts that I should be deleting?

Was this reply helpful? Yes No
ESchmidt 6 on at

Like (2)

Report

I have the same problem on a flow created today, which obviously does not use components removed in 2016.

Seems Power Automate is not a production ready product.

Was this reply helpful? Yes No
nirav_2052003 6 on at

Like (2)

Report

I agree. I am facing the same error as mentioned in this thread on a flow that has been working fine since its creation two weeks ago.

Power Automate is not a production ready product. I would request product team to fix basic issues and not release features without proper testing.

Please help us.

Was this reply helpful? Yes No
DeeDAYv 3 on at

Like (0)

Report

I have tried the export / import thing and still get the error on two actions. I can delete them and the error goes away. Has anyone had help on this?

Was this reply helpful? Yes No