cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
KimP
Frequent Visitor

Error editing existing (working) Flow

Hi,

 

See below screen shot.

 

Error Screen Shot

 

This flow is working and has been for months. I just went in to edit the string in the Condition and click save. Nothing else has changed.

What I've tried:

  • Clearing cache
  • Private browsing
  • Chrome and Edge browsers
  • Signing out of account

None of these have resulted in any different error.

 

Any help appreciated.

 

Thanks,

Kim

1 ACCEPTED SOLUTION

Accepted Solutions

The issue appears to have been resolved.

 

We now get no stupid error message when saving a perfectly normal workflow. Thank you Microsoft.

View solution in original post

9 REPLIES 9
v-litu-msft
Community Support
Community Support

Hi @KimP,

 

Did you change the trigger in the past time?

  • You can have a tested that Save as a copy Flow, then open the copied Flow to run.
  • Or you can export your Flow, then import it, recreate the connection of the Outlook connector.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

yashag2255
Dual Super User II
Dual Super User II

Hey @KimP 

 

The error states that there is a problem with the trigger. Can you try deleting that trigger and add a new one over there? Can you check if that resolves the issue and if not, share a screenshot of the entire flow so that we can take a look and better identify the issue?

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

KimP
Frequent Visitor


@v-litu-msft wrote:

Hi @KimP,

 

Did you change the trigger in the past time?

  • You can have a tested that Save as a copy Flow, then open the copied Flow to run.
  • Or you can export your Flow, then import it, recreate the connection of the Outlook connector.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 


The trigger has not been changed.

To be clear, this flow is working, it is still working, I can see it successfully completed today.

All I was trying to do is change the string it searches for in the attachment.

 

yashag2255
Dual Super User II
Dual Super User II

Hey @KimP 

 

This issue has been observed in many triggers for the UK tenants yesterday: https://twitter.com/Appolotech/status/1182254701036875776

 

I would recommend to create a support ticket and check with the team if it is a tenant specific issue here: https://us.flow.microsoft.com/en-us/support/

 

Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

I am suddenly having the same issue here in New Zealand. Flows that have worked for a long time and still run, now cannot be saved even with no edits. The error occurs on out-of-the-box Flows as well.

 

The error text is: The template validation failed: 'The 'recurrence' property of template trigger 'When_a_file_is_created_(properties_only)' at line '1' and column '1265' is not defined or not valid.'.

 

I think Microsoft have broken something. Hopefully the issue will be fixed in the next day or so.

 

Screenshots:

 

Test Flow with error messageTest Flow with error messageThe offending scriptThe offending script

Hey @sminhinnick 

 

Please refer to my earlier response and create a support ticket for this. I am sure this is being worked on as there have been a couple of incident reports in this in the past 24 hours or so. 

 

Hope this Helps!

 

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

Thanks @yashag2255. Yes, I believe my work colleague created a support ticket for this error. If the problem is still ongoing on Monday I will confirm this has been done.

The issue appears to have been resolved.

 

We now get no stupid error message when saving a perfectly normal workflow. Thank you Microsoft.

View solution in original post

KimP
Frequent Visitor

Working for me now also. Thank you.

Helpful resources

Announcements
User Groups Public Preview

Join us for our User Group Public Preview!

Power Automate User Groups are coming! Make sure you’re among the first to know when user groups go live for public preview.

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (28,437)