Timeouts
Timeouts occur when one or more of the elements in your test session becomes inactive for a specified period of time. The different timeouts that might be encountered in the logs:
| Timeouts | Description |
|---|---|
| SO_TIMEOUT | The hub waits for a maximum of 240 seconds before an unresponsive app is killed, changing the session status to ERROR on the dashboard. |
| IDLE TIMEOUT | If a session is idle for more than 90 seconds, the session is stopped, changing the session status to TIMEOUT on the dashboard. |
| SESSION LIMIT REACHED | If a session is running for more than 7200 seconds (2 hours), the session is stopped, changing the session status to TIMED OUT on the dashboard. |
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Is this page helping you?
Yes
No
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Talk to automation expert