Flow Designer - Configuration for Max Results on filter conditions and Look up records

[sivachandup]

Hi Team,

Can anyone help me here to understand, how many max results that we can Include in Flow designer as shown in picture below. Is there any limit to it by service now that we can only include to specific number. Because I'm working on Incident table as we know this is a huge table with lot of data. As per my requirement I am auto resolving records based on condition mentioned in image. And this flow triggers on daily basis at 6:00 Am. Since I set Max results to 1000 and flow is only updating around 1000 records it seems. But there are other bunch of records still not getting updated due to this. My question here is :

1. What if we leave it to empty ?

2. what if we Increase the number count to big number like 10000 or 100000 for example. Does this high number effects the efficiency of flow designer or it throws any kind of errors.

Kindly explain, Thanks in advance.

[pavani_paluri]

Hi @sivachandup ,

Leaving it empty could fetch 100 records only because its the default limit. You can do it, but it’s not a good idea because it could slow down instance and its not efficient.

You can achieve the updating of large number of tickets by using batches. Run the flow in parts (e.g., 1000 records at a time) or a script or split the records by a condition (like date, group, etc.) in multiple flow.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P

[sivachandup]

Thanks for response @pavani_paluri 

I was thinking in another approach, what if we use scheduled job to do the same. since it is a server side script and runs on daily basis. It doesn't have any limitations of max results unlike Flow designer. As long as the filter criteria matches it will pull up all the records(even it is a huge count) and update all Incident records as mentioned above. What will be your suggestion on this ? Am I thinking in correct way.

Kindly respond. Thank You again.

[pavani_paluri · Accepted solution]

Hi @sivachandup,

Yes the scheduled job will also work and it can huge number of tickets as well.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P

[Community Alums]

1. If you leave it as blank, it will pick up the default value configured in your instance. OOB it is 1000.

2. You can increase the number however it will result in higher flow execution time which can impact the performance. If your flow execution time is taking more than 30 seconds, it might get timeout as well since FlowAPI OOB is set to timeout after 30 Secs.

You may increase the value based on the system property if need be.

com.glide.hub.flow_api.default_execution_time 

However you may also need to check the performance impact.

If you feel, my response is useful, Kindly mark it as Helpful.