Workflow behavior when MYSQL is down

Hi,

With current implementation, if MYSQL server goes down then all workflows which are in in progress state goes to stopped state or remain in the same state. From UI, they appear to be stopped but from backend (Mysql) table they still are in progress . Therefore, the status api returns results which says that the workflow is still running. This behavior is seen in innodb cluster setup when there is a failover from master to slave.

These workflows then need to be cleaned up using DB script and ES script.

This request is change the behavior to move the workflows to failed state and gracefully remove them from running queue.