There are cases of "architecture by happenstance" where a rewrite is your only path forward ultimately. Developer understanding of the specific business needs often evolves over time and poor choices were made in the beginning. You can rearchitect it in place over 5 years or you can do it in six months. It helps to have a leader with a strong vision and sense of where things went wrong the last time, though. If it's just a bunch of "this app sucks. We need to rewrite it in .Net/NodeJS/etc." then you're doomed to fail in all the same ways.

I ~~took place in~~ bailed on a Java -> .Net migration where they were literally copying and changing syntax. It could've been a singular opportunity to fix a bunch of things, but was instead a waste of money and probably 60 developer years. I wonder if they ever finished...