"Limitations for iOS" states that there is a 10-second limit on processes that involve communication.
HCL Nomad network requests are limited to 10 seconds. If latency between the client and a Domino server causes network operations to exceed this limit, then normal operations can fail.
This limit applies not only to GPS and HTTP but also to NRPC communication with Domino.
We'll call this the "10 second limit".
I created an agent in LotusScript that reads all the entries in the view in order, with a loop.
When I run this agent on the Notes client, it takes over 200 seconds to finish. When run on the server, it takes 20 seconds.
I added an ON ERROR statement to the agent so that we can see why the process is finished. We also added code to Sub Terminate to display the message.
When I run this agent on Nomad, it exits successfully in less than 9 seconds, or ON ERROR statement and Sub Termination is not executed.
In other words, the agent found that the ON ERROR statement does not work if it exits with a "10 second limit".
If the agent is unable to handle errors that occur at the "10 second limit", it is not only unable to indicate to the user the reason for the termination, but it is also unable to execute code to follow up on the error when it occurs.
For example, if an agent running in the Notes client is in a perpetual loop and Ctrl + Break forces it to exit, it can be handled as an error. I'd like to be able to reliably handle an error when the "10-second limit" occurs in Nomad as well.