If Runscope is unable to communicate with your agent regularly, test results that attempt to use that agent will be marked as Remote Agent Expired. Here are some steps you can follow to help debug this issue:
--versionflag, and you can download the latest version here.
--verboseflag when running the agent to get a more detailed output.
https://www.runscope.com. Check our Agent Connection Errors and HTTP/HTTPS Proxy Setup articles for more information.
[ERROR] No open slots for work, that means your agent is trying to run more tests than it can handle. To fix this, update your configuration file to use
disconnect-timeout=15. That setting determines how long Runscope will wait before considering the agent offline, so increasing the timeout can potentially fix the issue. The only drawback for increasing that value is that when you turn off the agent, the UI will take longer before showing it as offline.
If your tests continue to expire after following the steps above, please contact support.