Drıftstack docs
Docs

Proxy test says ‘Driftstack was busy; try again in a minute’

You might be here because: “Driftstack was busy try again in a minute” · “our test service is busy right now” · “no proxy results landed — run Test all again” · “the check could not complete” · “not measured yet Driftstack was busy” · “proxy test keeps skipping”

Short answer

This is not a result about your proxy — nothing was measured. The machine that runs full checks was busy or the request timed out on Driftstack’s side. Wait a minute and run the check again. Your proxy is not marked as failed and its earlier readings are kept.

Check first

  • Signed in and online?
  • Did you run several checks at once (Test all over many VPN rows)? They queue for the same machine.

Likely causes and fixes

  1. “Driftstack was busy; try again in a minute” in the Test-all tally. Re-run Check VPN on that row after a minute.
  2. “Driftstack could not run this test right now; try again shortly” / “the check could not complete; try again shortly”. Same class — retry.
  3. The QUIC chip says “Not measured yet — Driftstack was busy…” and the latency side shows “busy”. Nothing is wrong with the tunnel; test again in a few minutes.
  4. “No proxy results landed — run Test all again.”. Run it again.
  5. “VPN checks are not available on this deployment.” A retry will not change that.
  6. API caller. An ok: false with not_run set (no_node / check_unavailable) is not a failed proxy; branch on not_run before treating it as one.

If it still fails

Rule of thumb: if every check for more than a few minutes ends busy, press Talk to a person in this chat (or open Help) and include the time window and the proxy labels — that is on Driftstack’s side and a person should look.