Currently StackState supports a limited number of actively running checks. If this limitation is reached, an error will appear to the checks that were not started due to this limitations. If this happens one of the following actions can be taken:
- If you run a development setup, upgrade to the production setup
- Reduce the amount of checks synchronized though the synchronization framework
The kubernetes-based StackState that is currently under development will support scale-out of runnable checks. When exactly scale-out of checks will be released as a feature is to be determined.