Task off hold on specific date - best practice suggestion

[M_iA]

Hello,

I am trying to decide how to manage tasks that are put on hold until a specific date/time.

I have 3 choices really:

1.Have a scheduled job run every 5 minutes to check "on hold until" field and if earlier that current date/time, to push to in progress

2.When an agent adds a date/time to the field, flow is created and waits until the date/time

3. Use an internal OLA thats created when date/time added and is completed when time is reached and therefore pushes to work in progress.

Issue with 2 and 3 is that if the agent changes the date time! With number 2 and 3, Probably need to put in a loop into the flows to check date/time on a daily schedule and use the updated date/time.

So leaning towards option 1. But my concerns would be performance related and would this have much of an impact? We have quite a mature instance and probably dealing with 3k new tickets every day so running these scheduled jobs every 5 minutes on tables that have 20/30k active tickets might have an impact?

Then theres also the fact that with running these jobs every 5 minutes, its not an instant off hold.

Any thoughts / opinions would be greatly appreciated

[Dr Atul G- LNG]

Hi @M_iA 

What did you do with the date field though for people who changed it after the initial save?

Atul : Yes, it must allowed but you make comments mandatory so that agent need to add a justification.

Was it a case of educating?

Atul: If you want to over above point, then i will its education and maturity only.

Or have you put a scheduled loop in the flow to keep checking the date to see if changed?

Atul: Loop is must as date has been changed 

[M_iA]

Many thanks for the insight @Dr Atul G- LNG

[Dr Atul G- LNG]

Hi @M_iA 

if you happy with answer, please accept solution and close the thread.