When using the SAP.ReadStatusbar activity, if your SAP session is disconnected, hangs or has a execution timeout (anything that keeps the gui scripting busy), the timeout will never be triggered so no system exception is triggered.
Whilst a rare combination of events, we have experienced this issue a few times in production. Our current workaround is to have a parallel process with a stopwatch running to kill the sap session after our maximum wait time has been reached. Once the SAP process has been killed, the selector will fail and trigger a system exception.
Would be great if this activity behaved as others do and stick to the timeouts.
Activity pack(s) used;