07-09-2020, 07:18 PM
Thanks Dan.
It's compiled under Seattle, though on subscription so all versions available, and it's IW15.2.3.
Yesterday we could only recreate by adding a sleep to button click, but disabling the button in the onClick event cured that.
The only clue is it would appear around the busier times when sessions are in the order of ~300 yet this afternoon issue was ~60 sessions connected.
Since the last restart this afternoon, which isn't a busy time of day, I've recorded the time from the CallBackResponse to the OnSignature event and it runs from ~100ms to 14seconds.
I'm pretty sure during busy periods the elapsed time as been into the minutes, which would would be the issue if the IWLocker progress is clearing at the end of the Async event and the ActivateLock(), the form is not locked as not in a submit, so everything is active, waiting on the callback, and the end user is just clicking submit or cancel as they think the app s dead.
It's compiled under Seattle, though on subscription so all versions available, and it's IW15.2.3.
Yesterday we could only recreate by adding a sleep to button click, but disabling the button in the onClick event cured that.
The only clue is it would appear around the busier times when sessions are in the order of ~300 yet this afternoon issue was ~60 sessions connected.
Since the last restart this afternoon, which isn't a busy time of day, I've recorded the time from the CallBackResponse to the OnSignature event and it runs from ~100ms to 14seconds.
I'm pretty sure during busy periods the elapsed time as been into the minutes, which would would be the issue if the IWLocker progress is clearing at the end of the Async event and the ActivateLock(), the form is not locked as not in a submit, so everything is active, waiting on the callback, and the end user is just clicking submit or cancel as they think the app s dead.