We implemented Try-Catch for a Web login page that requires some additional WF Executor steps.
The issue we found is that processing is being delayed about 30 seconds before marking the Catch step as executed.
Is this normal behavior or should we look at some WF we developed?
Before the existence of Try-Catch logic, login was like a breeze.
Try-Catch relieves many of the error processing hurdles but is this the tradeoff we should expect?
Thanks for any imput
1 Like
Hi! Willem,
When you use Try-Catch steps the workflow may be a little slow as it checks the conditions for each step.
1 Like
We experienced, that if more steps are involved, longer it will take to move forward.
If more processing power is applied, will this improve?
Try-Catch very useful for faster implementation but performance wise, capture error on each step and manage it accordingly.
1 Like
