The end points to remove a bad schedule that otherwise may prevent the scheduler to start have been introduced in 2.3.4 release. However rare this may be, the hung schedule for the app or driver is not easily identifiable by the user, so our engineers will add a warning in the log (past logs) to indicate which app/driver may have a bad schedule so that the user can take the corrective action of removing it, without the need to reach out to us.