L3 - Default Description
Context:
Currently Optimize is trying to connect and validate the connection to every configured camunda engine on startup.
As soon as at least one engine fails this check the startup is aborted. This is intended as it forces the administrator to validate and address any misconfigurations immediately, rather then only noticing setup problems later on during operation.
Once Optimize was started up successfully, connected engines are allowed to go down which is monitored in the engine connection status and reflected in the Footer in the web-interface of Optimize.
However there are scenarios, especially when a considerable amount of engines are connected, where at any point in time when Optimize needs to get restarted not all engines are reachable. The current behavior in such cases (e.g. maintenance of an engine) prevents a successfull restart of Optimize and the usage of it for users of the engines that are actually reachable.
AT:
- there should be a possibility to allow Optimize to start even if Optimize cannot connect to some/or all engines (or all)