Dataverse for Teams & Automated flows trigger frequency

[mrQ]

Dear all

I've recently started to use Dataverse for Teams. Before that, all my data have been saved in SharePoint and so my flows attached to a list in SharePoint were triggered automatically when someone created a new item.

Generally, the flow attached to a SharePoint list got automatically triggered within 1 minute. I can't remember / don't think it was more than that so far.

When I use Dataverse for Teams and I use the "When a row is added, modified or deleted" trigger in Power Automate, I have to wait around 5mins or sometimes even more for the flow to start. 

I couldn't find anything in the documentation that differentiates the frequencies between SharePoint and Dataverse for Teams (it's also just too much... maybe someone else knows its there and can point me to the article?), but has anyone experienced this as well? 

If that is the case, that'd be a killer criteria for us to use Dataverse for Teams 😞

We don't have any special Power Apps (per user/per app) or Power Automate (per user/ per flow) plans.

[Pstork1]

Actually, your memory about the trigger times in SharePoint is mistaken.  Triggering a flow based on When an Item is created or modified can take anywhere from 0-5 minutes.  Its often faster than 5 minutes, but the polling interval is 5 minutes.  Dataverse should be about the same.  Its also more immediate when testing in SharePoint than it is in production.  That may be why you remember it being faster.

[mrQ]

Hi @Pstork1 

Thanks for your response.

Since I've been using it super intensively, I couldn't really believe that I ever waited 5mins in SharePoint so I went ahead and made some tests:

10:57	test1 dataverse	started
11:41	test1 dataverse	executed
11:26	test2 dataverse	started
11:51	test2 dataverse	executed
11:02	test1 sp	started
11:03	test1 sp	executed
11:13	test2 sp	started
11:14	test2 sp	executed
11:14	test3 sp	started
11:15	test3 sp	executed
11:21	test4 sp	started
11:22	test4 sp	executed
12:06	test5 sp	started
12:07	test5 sp	executed

It looks like the dataverse for teams trigger does not have an interval of 0-5mins. It's a crazy lot more than that, unfortunately.... I'm not sure if this is something related to my tenant/environment. It would be great to know if someone else could make a similar test...

SharePoint, on the other hand, is always being triggered within 1min, not 0-5 (I thought I was lucky with the intervals on the first test so I made a total of 5).

Do you think you could conduct such a test as well or do you think I should get in contact with MS support directly?

Thankful regards!

[Pstork1]

I'll run some tests today and see if I get similar results.

[Pstork1 · Accepted solution]

I just finished some testing with Dataverse for Teams.  My results are as follows

First trigger - 12 minutes

Second trigger - 6 minutes

Third trigger - 2 minutes

Given the spin up time for JIT I'm not surprised by the first one being longer.  The 6 and 2 are more in keeping with what I expect.  This is in the US region.

[mrQ]

Thanks @Pstork1 

What is JIT? 

I'm in Europe... that's weird. 

I'll mark your response as solved (since it's more like a "normal" result) and will open a ticket with MS regarding my long intervals... 

[Pstork1 · Accepted solution]

Sorry for the acronym.  JIT stands for Just In Time.  Microsoft has a tendency to store code in something other than a directly executable format.  So the first time something runs it has to translate from that format to actual executable code. After doing that once the executable code is normally cached for several hours.  So the first invocation, or the first invocation after no invocations for a number of hours can take longer.

The trigger time could be region related, but I wouldn't think it would vary that much for Europe.  You might want to open a support ticket to get MS to check it. I don't think your trigger times are the normal expected times.

[mrQ]

Thanks again 🙂 I'll do so

[mrQ]

I was in contact with MS Support. At first the trigger had the same behaviour - so it was good that MS saw it, but the next day everything worked by design. Max of 5min trigger frequency. 

I guess this was just an unreported-outage/issue 😞 

@Pstork1 

Thanks for your help.