Knowledge Base

  1. Home
  2. Knowledge Base
  3. Technical Support
  4. Troubleshooting
  5. What to do when “No agent available to run test at [XXX]”
What to do when “No agent available to run test at [XXX]”

testRTC uses a mixture of static and dynamic machines to host its probes. When you start a test, based on the test’s characteristics, testRTC would decide if it should be allocated from the existing pool of machines or dynamically spawn machines for that purpose.

While we try to monitor carefully the utilization of our machines and service, there are peaks in usage by customers which may cause the static machines available to deplete. When that happens, your tests will fail with a failure reason that reads something like this:

No agent available to run test at [East-US] project: …

Here are a few approaches for you to handle such a failure:

  1. Retry – try to execute the test again after waiting a couple of minutes
  2. Force dynamic allocation – you can add #dynamic-probe:true to the run options of the test
  3. Switch region – try using probes from other regions, where load might be lower

When forcing dynamic allocation, there will be an extra allocation time taking place which can make the test slightly longer (usually by a minute or two), which is why for tests with a low number of probes, we usually suggest not to switch to dynamic allocations.

Was this article helpful?

Related Articles

Leave a Reply 0 comments

Leave a Reply: