Posted: 15 Mar 2018 9:10 EDT Last activity: 19 Mar 2018 2:55 EDT
How to keep user browser alive when multiple automated process are running in backend one after another
We have a case having a stage with process flow where we have multiple steps (1 - 5). Step one is a manual input step where user provides details and submits. Step 2,3,4 are automated steps connect rest calling some services. Each process taking around 2-3 mins. If anything fails it halts the further execution and returns to the user screen. However if all the steps go through the user session receives the data only after all steps are complete i.e. approx 9 mins. Since server timeout is set at 5 mins, although the process completes in backend user sees a white screen with error. We have tried increasing the server timeout parameters which works but has adverse effect on the system. Default timeout is 5 mins.
Is it possible to maintain the connection to the browser live by establishing connection each time any step completes. That is step 2 completes as success the timeout is reset and the calculation again starts for step 3 and so on, there by ensuring the timeout is effective for each backend call rather than all together.
After the step 2 is there any UI interaction happening? Can you try to keep the busy indicator in the UI till that time (or try to invoke a busy inidactor function call after ecah stage which depends on your application design).