Concurrent Crawl Limits about browsertrix HOT 4 CLOSED

A question: should there be a separate setting for max queued crawls as well as max concurrent crawls?
Without the latter, the user can still set an unlimited number of crawls to be waiting in the queue, even if only 1 or 2 may run at a time. With this limit, we could also limit how many crawls can be in waiting state (beyond that, it would be an error). Relatedly, this could apply to how many crawls could be set to be scheduled (though not necessarily run) at once.
This would then have further limits of:

• number of concurrent crawls that can run at once
• number of crawls that could be queued at once
• number of crawls that could be scheduled at once (should be <= queued count?)

Or is this perhaps too complicated at this stage?

from browsertrix.

UI support tracked via #867

from browsertrix.

Should we see if we want to limit max queued crawls first? Overall not a bad idea, I imagine this would disable certian options in the workflow actions & config screens, so there would be front end impacts, but would be nice to see what average usage is like before we set more restrictions?

from browsertrix.

This is also done! 🎉

from browsertrix.