We have an issue during failover where our production databases will go into Initializing state. It is random, not consistent. We've done a lot of investigation, debugging and are stumped. The systems are relatively quiet when we failover. We have scripts that check the log send queue, redo queue, and AG health status. The only way to get the databases out of this state is to kill the SQL Server process in task manager. That's right, we have to kill the executable. When we restart, the databases will go into restoring state (I think that is the state). From there, we have to drop the database and add it back into the AG. Anyone have a similar issue? This only happens to our production servers not our DEV or QA AGs. It's frustrating. Been trying to figure it out for well over a year. Even MS and a consultant we worked with couldn't figure it out.