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

"When an item is created or modified" is trigger by http request with "bNewDocumentUpdate" set to true.

My flow is trigger when an item is created or modified on Sharepoint. In my flow I also use a "send an http request to Sharepoint" and the body look like this:

 

{
"formValues": 
[
{"FieldName": "Approved", "FieldValue":  "Yes"}
],
"bNewDocumentUpdate": true
}

 

Request doesn't change the version of item, so it should not trigger a flow again and create an infinity loop.

4 REPLIES 4
Alicja
Frequent Visitor

Update. There is a second bug. 
Every recursively running flow was sending me an e-mail, so I deleted this flow yesterday. 
Despite this, I still get emails from this flow. Removing the process did not affect its stopping.

I'm making changes to the files which flow uses to force this processes to fail.

Can I get some information about your solution of this problem?

 

 

Hi @Alicja,

 

Sometimes when you delete a flow you'll get this 'ghost' process still running in the backend even though the flow has been deleted.

This should be cleared after awhile but if you keep getting emails from the old flow, please open a support request through the Power Platform Admin Center and Support will delete it for you.

 

Thank you,

Ovidiu

Alicja
Frequent Visitor

I've changed the one file name, which this flow used to make the 'flow ghost runnings' stop, so I don't have problem with that. 
I would like to know if using "bNewDocumentUpdate" set as true in Sharepoint http request should modifing the event and run flows or is it only a temporary bug. 

Alicja
Frequent Visitor

It was not the problem. I'm still waiting for answer to my first question. 

I would like to know if using "bNewDocumentUpdate" set as true in Sharepoint http request should modifing the event in calendar and run flows or is it only a temporary bug.
I would like to create flow, triggered by "when an item is created or modified" in Sharepoint calendar and in the same flow change this event data by using http request, which doesn't change the version of this event. It was working for me for a few days and then suddenly stopped to work (it started recursively evoke).  That is what I was asking. 


Where is the bug? 
Is it a bug that flow suddenly stopped working for me? Or is there any error ocurred on your side when my flow was working for a few days and it really should never work for me?  
This is my problem. 

Can I expect that you repair this bug or should I assume that this bug will not be fixed, because it shouldn't have worked? 

Helpful resources

Announcements
Process Advisor

Introducing Process Advisor

Check out the new Process Advisor community forum board!

MPA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Top Solution Authors
Users online (26,849)