There's a problem with the flow's trigger

[sashkashurik]

Getting a 410 error on a flow from a template that I have been using for a while now.  The template does not exist anymore but the trigger does. What happened?

Detailed body of error: 

{

"error": {

"errors": [

{

"domain": "calendar",

"reason": "updatedMinTooLongAgo",

"message": "The requested minimum modification time lies too far in the past.",

"locationType": "parameter",

"location": "updatedMin"

}

],

"code": 410,

"message": "The requested minimum modification time lies too far in the past."

}

}

Note: I have three flows like the one above. All display the same message and have been working recently (something like a week ago or even a few days ago all was fine). Now, all three flows show no history of runs and display the above message.

[v-litu-msft]

Hi @sashkashurik,

Could you please share your Flow Trigger configuration and the action with the error "410 Gone"?

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.

[sashkashurik]

The flow was created (without any major modification) from a template named: Google calendar sync to Office 365 calendar that was available until sometime in june this year.

 

Note however, that the error is there NOT following an action! The error shows up when I click on "Fix the trigger" link on one of my previous snaps.

There is no history of execution with failures and for some (I have three almost indentical flows) no history of execution at all despite the fact that all flows have run multiple times successfully for months.

[v-litu-msft · Accepted solution]

Hi @sashkashurik,

There is some issue with my Google Calendar trigger, but it is not the same issue with your, it is out of quota, I try to recreate the connection of Google Calendar, then it was fixed.

So, you can recreate the Google Calendar, then try it again.

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.

[sashkashurik]

Hi,

Thank you! Creating a copy of the flow solved the issue. 

However, I do not understand why it happend in the first place? How would I prevent it next time? How can we debug it? How can I support users with the same issues?

[v-litu-msft]

Hi @sashkashurik,

This problem happens occasionally, and if it does, recreate the connection and it will be solved.

Best Regards,
Community Support Team _ Lin Tu

[sashkashurik]

I do understand and we will not debate about it. However, flows are ment to be reliable. If I configure a flow, I do not want to go back every 3 months to redo it. 

Similarly, if I configure a flow for a client/user I will have to waste my time and money to go back and make copies etc.

Is there a metric that can tell me when the flow will fail? How can we prevent this? Microsoft must know why this happens and hoepefully some users too.

[Y_R]

Hey @sashkashurik ,

I have been having a very similar issue with respect to the erroneous trigger issue. Even though my error messages are slightly different, I always have to go back every few weeks to be presented with the same "Fix the trigger" issue. As you said, it's tedious to constantly keep going back to fix these things especially when it's provisions to a client environment. This definitely proves that Flow is unreliable since no one can seem to provide a solid explanation as to why this is occuring.

The thing is, it's a very serious issue because when the Flow breaks like this, ALL processes goes down and whatever the Flow is paired with is not useable! This is a terrible experience in a client's environment and I really wish that a fix can be provided for this.

[sashkashurik]

To be fair, I have opened a ticket with Microsoft on the issue and they were willing to help. However, I have no time for multiple phone conversations repeating the same thing over and over: I had to close it because I found a way to make flows work again and they kept insisting on talking to me on the phone instead of reading my emails.

One thing for sure: it keeps reoccurring for me and I still haven't found a solution anywhere on the net.

[Y_R]

Hey @sashkashurik ,

Thank you for sharing the fact that you opened a ticket. I was about to go that route until I read your reply.

I have also found a way to make it work in the meantime: I add temporary Trigger, delete the erroneous one, then re-add it as the main trigger and delete the temporary one. The error goes away for a while until it randomly shows up again and I find myself having to repeat this method too often. It also prevents the Flow from kicking off.

Currently, I am experiencing this issue with almost ALL my Flows. The error messages pop up on random days and times. It's really frustrating...

[Anonymous]

Having the same issue here as well but recreating the trigger produces the same issue for me now. Hoping this one will just get fixed "magically" I guess.

[Y_R]

Hey @Anonymous 

You're right. It seems that recreating the trigger is not a "ratch" way of fixing this anymore as it still occurs immediately after you switch them out. I noticed because since the last time i've done this, I rechecked the same Flow, only to be presented with the same error message, and attempted the "ratch fix", but no avail.... I am very worried, because most of my Flows are very large and in order to recreate from scratch, a lot of time that I do not have will be taken to do so. And because the "export to a zip file and import into another environment " method is the sole cause of this trigger issue we are all experiencing.... What are we to do?