Transcript:
0:00 [Music]
0:04 Hi everyone, this is Patrick from North
0:07 52. In this video, I'm going to discuss
0:10 the advanced fields that are available
0:12 in the NOR
0:14 52uler. In most instances, it would be
0:16 unlikely that you would need to access
0:18 these fields, but they do exist if you
0:21 need
0:22 them. We start by opening the happy
0:25 birthday schedule we created in the last
0:27 video.
0:29 Click on N52 commands toggle advanced
0:33 view. As you can see, lots more fields
0:36 have appeared on the schedule. The
0:39 important fields that we will discuss in
0:41 this video are the query record limit
0:43 and the max infinite loop
0:45 depth. We start with max infinite loop
0:49 depth. In Dynamics 365, Microsoft has
0:53 infinite loop detection. If a workflow
0:56 or process enters an infinite loop,
0:58 Microsoft will stop it. Loop detection
1:01 works by analyzing the depth of a system
1:04 job or plug-in. When a workflow starts,
1:07 we are at a depth of level one. If that
1:10 workflow triggers a child workflow, it
1:12 goes to level two. That child workflow
1:15 does some updates on a record level
1:18 three. Those updates fire plugins. Level
1:21 four, which create new records. Level
1:24 five, which triggers workflows. Level
1:26 six, and on and on it goes. For onremise
1:30 Dynamics 365, the out of the box
1:32 infinite loop detection triggers at
1:34 level 8. For online, this happens at
1:37 level 16. If you are using a schedule to
1:40 trigger a workflow and your workflow
1:42 start failing with warnings about being
1:45 in an infinite loop, then it is possible
1:47 you are generating a false positive
1:49 infinite loop warning. A false positive
1:52 is where your workflows are carrying out
1:54 so much work Microsoft thinks becoming a
1:57 loop. N52 can protect you from false
2:00 positives through the max infinite loop
2:03 depth field. As the schedule executes,
2:06 we can listen into the current depth and
2:09 then pause the schedule once the depth
2:11 reaches the value stored in this field.
2:14 When the schedule pauses, it will wait
2:16 for 1 hour, which will force Microsoft's
2:19 infinite loop detection to reset back to
2:21 zero and then the schedule will continue
2:24 on. Please note that it is possible on
2:27 premise to use supported PowerShell
2:29 commands to raise Microsoft's infinite
2:32 loop detection level. I have included a
2:34 link on how to do this in the video
2:38 description. The second field is the
2:41 query record limit. Let's say your fetch
2:43 XML returns 10,000 records. If you
2:46 trigger 10,000 workflows at once, your
2:49 Dynamics 365 environment will most
2:52 likely time out most if not all of the
2:54 workflows and they will all be in a
2:56 failed state.
2:58 With query record limit, we break up the
3:01 10,000 records into more manageable
3:03 sections that we can then process in
3:05 batches. In this example, we will
3:08 process 250 happy birthday emails at a
3:11 time. We will process them until we
3:14 reach the max infinite loop depth
3:16 specified in the other field. Then the
3:18 schedule pauses for an hour before
3:21 continuing on.
3:23 Thank you for watching and if you have
3:25 any questions, please contact
3:28 support@nord52.com or visit
3:29 support.North52.com.