Power Platform Community Forum Thread Details

I have a flow that randomly (at least it seems random) missed to be triggered.

Flow A: marks the item as ready to submit

Flow B: is triggered on When item is created or modified, looks if item is ready to submit and then submits it.

Here's an example from the Sharepoint Item's Version History:

When the item was first updated as "Ready to submit" Flow B never triggered. It didn't even run. It's not like it ran but didn't find satisfactory conditions to conclude. It simply didn't even run.

However, after I reverted the item to its prior version and re-run Flow A to re-mark it as ready to submit, Flow B miraculously picked it up and ran as normal.

I then went to cloud flow activity and found no errors.

I then tried the flow's own analytics where I found errors but none of them from the same day or relating to this case.

In fact I check those errors back and it seems that they self resolved at a later point without intervention.

UPDATE

I went to the all flows list and filtered for "Failed Checks":

I found a fair bunch:

Every single one of them had the error message:

The API 'sharepointonline' returned an invalid response for workflow operation 'When_an_item_is_created_or_modified' of type 'OpenApiConnection'. Error details: 'The API operation 'GetOnUpdatedItems' is missing required property 'body/value/0/field_20'.'

Ha! I though I had this sorted.

So off I go to the list and went straight to the column corresponding to 'field_20':

but the bloody thing isn't a required field:

so someone, somewhere put it into its thick skull that the field is somehow "required".

What's best, I checked various successful runs where the field was actually empty (so it didn't stop the flow from triggering!).

So right now, I'm at a loss as to where to look to start troubleshooting those random errors.

I've already put together a little flow to send me alerts when items are marked as Ready but not processed for over 2 hours so I can keep track for recurrences.

Any help would be welcome.

P.S. The flow has been unchanged since its inception two years ago and has been operating without issues (till now).

Categories:

Using flows

The only condition is when item is created or modified. No other condition.

What seems to have fixed it was swapping one SharePoint connector with one of the other 3 SharePoint connectors that I have in my name.

What's even funnier, is that while the SharePoint connector is classed as standard when looking at the connectors manifest of my flow I notice that one of the two SharePoint connectors was classed as "Enterprise" and the other as "Free". Well, guess what, I don't have any elevated sub package and I only piggyback and play around with the basic E3 standard connectors and capabilities.

So if "Enterprise" was meant to signify some sort of premium flow/connector combo it shouldn't be working/available to me.

Maybe it's the fact that one connector was initialised way back in 2017 and the other is much newer being initialised in 2022. But still, none of this makes any direct, comprehensible sense....