Hi Matthew,
I just realised it’s not in the documentation, I’ll fix that, the reason you are getting a warning is the load on your agent machine is over 80%, in this case from your screen shot it’s memory consumption is over 80%, FYI if it goes over 95% it’ll show critical.
This warning status won’t actually stop you running a test, neither will a critical status, it’s there to get your attention that the agent is not in a healthy state for running a performance test, depending on your setup and number of robots you want to run you might be fine or it might be an indicator of why you are having issues, without knowing your setup, I don’t know.
As for not getting results on the run screen, it can take a little while for those to show up, how long did you wait? more than 5 minutes?
Just for some perspective, the time to first result showing is a combination of a variable portion of the polling time + time to run the first keyword + time to transmit the result back to the manager + refresh interval of the run screen (5 sec), worst case if they all line up for the maximum values this could be 17 seconds + the time to run the first keyword, but best case might be only a 1 or 2 seconds.
One suggestion, start with a small number of robots (5-10) and a slow ramp-up (>120 sec) till you get a feel for how it works, then step it up gradually to understand and what your agent machines are capable of. it varies a lot depending on your hardware and which robot framework libraries you use.
For example, if you are trying to run 100 robots on that agent with a 10 sec ramp-up and using SeleniumLibrary, you could be in a situation where 20 or even 30+ browsers are all launching at the same time which could strain the cpu and memory of the agent machine and cause a lot of disk reads at the same time, then because you are already memory constrained on your agent machine it might start swapping (more disk usage, showing things down more) or even worse the browser fails to launch from out of memory.
Hope that helps,
Dave.