Disregard my last comment. This was due to an internal change.
Hi @api.ben.overmyer, can I check what the status of this is now?
Is it still an issue? If so are you able to provide some Analysis IDs for failures?
Sorry for the radio silence. We’ve been working on reducing the number of (unnecessary) concurrent scans.
We’ll be testing whether this fixes the issue within the next few days.