Many times due to some performance reason , network latency , DB issues our workflows tends to slow down . during the pick hours these workflows are very much performance killers ans they keep consuming resources and make other important workflows slow down .
we should have some time limits where we should me mentioning how long my WF should execute and if wf is going after that it should be stopped .
following is one of the methods which can be achieved using timer and control tasks , using parallel tasks .
Here i am having session which is executing and with parallel timer task is also executing if my session execute s more than time we set in timer timer will trigger Abort task and workflow will get aborted
Abort task setting are as below
Happy learning :-)
we should have some time limits where we should me mentioning how long my WF should execute and if wf is going after that it should be stopped .
following is one of the methods which can be achieved using timer and control tasks , using parallel tasks .
Here i am having session which is executing and with parallel timer task is also executing if my session execute s more than time we set in timer timer will trigger Abort task and workflow will get aborted
Abort task setting are as below
Happy learning :-)