SharePoint Modified trigger does not work since few days (Checks No New Data)

[Anonymous]

I am using PowerApps to update a SharePoint list. Any time their is an item added to SharePoint list or an item is modified I run it through a flow to send emails.

Before I only used the SharePoint Modified trigger since it was bugged and triggered even when a new item was created not modified. It was fine since I set up my flow to account for that.

Now after the new update issues started to happen. Now the SharePoint Modified trigger does not trigger even when the SharePoint item is modified and not added it always skips no matter what.

The run always appears under Checks (no new data). So it seems that after the update it now fails to see that there is new data.

All those runs had modfied few fields in the item:

Here is the flow:

Here is the output:

{
  "Pragma": "no-cache",
  "Retry-After": "3600",
  "x-ms-request-id": "65bd61aa-405a-4f51-add7-df96f1d450aa",
  "Timing-Allow-Origin": "*",
  "Cache-Control": "no-cache",
  "Date": "Wed, 31 May 2017 20:19:20 GMT",
  "Location": "https://msmanaged-na.azure-apim.net/apim/sharepointonline/5b36bc45de37c22cfebd6e5a163730a2/datasets/https%253A%252F%252Faircanada.sharepoint.com%252Fsites%252FFPAPortal/tables/460f6b25-168d-43b8-af0f-49ea98ea2e21/onupdateditems?triggerstate=ZGF0ZXRpbWU9MjAxNy0wNS0zMVQyMDoxOToxOFo7aWQ9MA==",
  "Set-Cookie": "ARRAffinity=6f8192aeb45a330cdb5f642ecc217dcd76db8eb70939a923860f458883127859;Path=/;Domain=sharepointonlineconnectionprovider-westus.tip0-westus.p.azurewebsites.net",
  "Server": "Microsoft-IIS/8.0,Microsoft-HTTPAPI/2.0",
  "X-AspNet-Version": "4.0.30319",
  "X-Powered-By": "ASP.NET",
  "Content-Length": "0",
  "Expires": "-1"
}

Thanks for any help!

[douglasromao]

Hi @Anonymous,

Do you know if the user connection (the user that you are using at this trigger) had changed in the last days?

Regards,

Douglas Romão

[Anonymous]

Hi @douglasromao

No its same User its set up on my account. It does not work for me

[gamoraes]

Hi @Anonymous

Do you know if the List Name (Display Name) was changed?

I spent for this problem because Microsoft Flow uses the display name instead internal name.

Best Regards,

Gustavo Moraes

[Anonymous]

@gamoraesNo the List name remained the same nothing was changed.

Actually now I see very strange behavior which appears to be a bug. I am the only one who modifies the list and I noticed that suddenly the flow tries to run every hour and skips. Has anyone experienced this? No one has touched the list but it seems that flow is triggered every hour. Again this only started to happen after the update.

[gamoraes]

Hi @Anonymous it's really strange, i don't know how workaround

You can open a ticket in O365 support for this, I opened an about a month ago about a strange bug which was also just in one of my tenant.

If you do this, keep us updated.

Best Regards,

Gustavo Moraes

[v-yamao-msft]

Hi MartynasJurkus,

To test this issue, I create two flows, Flow1 is triggered by "When an existing item is modified", Flow2 is triggered by "When a new item is created".

Then I modify an existing item to trigger Flow1, but I found that Flow1 doesn't work. While when I create a new item, both Flow1 and Flow2 would be triggered and emails would be sent.

It seems that the trigger "When an existing item is modified" doesn't work as expected. I will try to report this issue on my side and back to you after I got any reponse.

Best regards, 

Mabel Mao

[v-yamao-msft]

Hi MartynasJurkus,

I have some updates for you.

PGs are working on a fix on this issue. It seems that it will be ok by the end of next week.

Please try it again at the end of next week and let me know if it will work as expected. I will also keep an eye on this issue.

Best regards,
Mabel Mao

[v-yamao-msft]

Hi All,

The fix for the issue has been rolled out. I test this on my side and it is working fine. Please try it on your side and let us know if you are still seeing issues.

Best regards,
Mabel Mao

[Anonymous]

Hi @v-yamao-msft

I tested it few times and there still are issues.

I have two flows (first with SharePoint Modified, second with SharePoint New)

I did several tests here are the results:

Test #1

Created 1 new item in SharePoint directly

SharePoint Modify flow: triggered (should not trigger)

SharePoint New flow: triggered (correct)

Test #2

Created 1 new item thorugh PowerApps in the SharePoint list

SharePoint Modify flow: triggered (should not trigger)

SharePoint New flow: triggered (correct)

Test #3

Modified 1 item in SharePoint directly

SharePoint Modify flow: skipped (should trigger, fix did not help)

SharePoint New flow: skipped (correct)

Test #4

Modified 1 item in PowerApps directly

SharePoint Modify flow: triggered (correct)

SharePoint New flow: skipped (correct)

You can see my previous tests here: https://powerusers.microsoft.com/t5/I-Found-A-Bug/SharePoint-Modified-trigger-strange-behavior/m-p/3...

So the problem is still there. The biggest surprise is that the Modify works correctly when item is edited through PowerApps and does not work when item is modifed through SharePoint. Also this might be a small test sample so I tried few more times:

Test #5

Modified 1 item in SharePoint directly

SharePoint Modify flow: triggered (correct)

SharePoint New flow: skipped (correct)

Test #6

Modified 1 item in PowerApps directly

SharePoint Modify flow: skipped (should trigger, fix did not help)

SharePoint New flow: skipped (correct)

After two more tests it seems that Modify flow triggers 50% of the time. Also I modified different items, but only one column.

I tried to make 2 more tests.

Test #7

Modified 1 item in SharePoint directly

SharePoint Modify flow: triggered 2 times (1 time for the modified item, 1 time for the item modified in Test #6)

SharePoint New flow: skipped (correct)

Test #8

Modified 1 item in PowerApps directly

SharePoint Modify flow: skipped (should trigger, fix did not help)

SharePoint New flow: skipped (correct)

It seems the problem is still there with the Modifed trigger although now it works more than before. Would really appreciate if you could look deeper in it as its quite an important flow for our organziation.

[v-yamao-msft]

Hi MartynasJurkus,

Thanks for your detailed testing results.

I also test this issue on my side again with two flows, Flow1 for “When a new item is created”, Flow2 for “When an existing item is modified”.

The results are:

Flow1: No matter a new item is created in SharePoint or through PowerApps, Flow1 can be triggered. There is no Skip in my flow.

Flow2: This flow will be triggered when a new item is created or when an existing item is modified. And it works both in SharePoint directly and through PowerApps. There is no skip in Flow2.

If possible, please provide more information so that we can take a further investigation on this issue. 

>An URL of your Flow. You could get the URL of your flow in edit mode

>Your Site/List information would be very helpful

Best regards,
Mabel Mao

[Per_Johansson]

Any results on these issues? I experience equivalent flow behaviour in sharepoint using flow.

[Anonymous]

Same issues here. Zero support received. Did someone accidentally release Flow before it was tested?

[Anonymous]

I am getting skipped on all my workflows when they should automatically run