Avatar

Community Advisor

Hi @Divya104 ,

 

No this way of workflow design is not recommended. It causes dead lock situations at some point because the scheduler next run and previous temporary table data are working on same table.

 

Also, your data will be misinterpreted because of the long wait time and shorter duration of scheduler.

As suggested by @David_Loyd , if it's necessary to wait for 2 hours, split your workflow in two workflows.

 

Thanks,

Jyoti