Planner Triggers - which is more reliable - When a task is assigned to me OR When a task is created?

[rnavrot]

Hello,

I am currently using When a task is assigned to me.

Here's what it currently does:

1. When a task is assigned to me, use Compose to Split title to grab the first few words.

2. Get details of task for later

3. Find row in Excel Table which is prepopulated with a bunch of other variables I need to grab these other variables

4. Create Sub-Task using info gathered from trigger, step 3, and step 2. 

5. Add description using Update task details

6. Store task details in Excel table for later

It works! BUT in my early phases of testing it does not seem to trigger immediately reliably.

The purpose of this Flow is to save our MGMT the time of having to re-create the sub-tasks (which are duplicates of the Main Task, just located in different Plans). 

How often does the 'When a task is assigned to me' trigger fire? It is not clear that it happens immediately, and it is not clear if there is a regular delay. As far as I can tell, when I assign myself a task Flow will sit there for a few moments before it actually duplicates my card.

What about 'When a Task is Created' trigger? This would work in my context, as I am only concerned with Tasks created on the main Plan, so I could point my trigger right at the Plan ID I need to use. But, will this trigger fire any more reliably?

Which of the two triggers in the title are more reliable, and does anyone know where I may find more details on how often these triggers poll?

Thank you,

-Ryan

[ChadVKealey]

Most of the "Automated" triggers (in my experience) are automatic, but not instantaneous. That is, they will fire based on the designated event, but not exactly at the moment the event occurs. Most of them work by polling the data source periodically for new data. For example, the SharePoint "when an item is created" trigger seems to poll on about a 5-8 minute interval. If an item is created right before that poll action occurs, it'll seem like the flow is instantaneous. However, if the item is created just AFTER the poll, then it'll take 5-8 minutes for it to run. I have yet to see a situation where it does not run (eventually). 

If you go to the All flow runs page and click the view drop-down in the top right, then select "Checks (no new data)", you'll see how often the flow is checking for new items/tasks, etc.

[rnavrot · Accepted solution]

Indeed. Showing 'Peek Code' on the triggers shows their recurrence frequency.

Any ideas on how to decrease this value? It looks like it is based on our organization's current PA Plan (In my case, comes with Dynamics). Not finding quick easy answers on faster polling frequency on the Microsoft site.

Thank you,

-Ryan

[ChadVKealey]

I suspect it's not something that can be explicitly changed, just a function of the license.