It’s a good question, and something we did discuss. Though, it isn’t something we can safely automate without days of testing first. We decided we’d use those days to work on a permanent fix and eliminate the issue instead.
Positive news - progress has been made, and we’re testing a fix internally.
Hopefully we’ll be rid of this once and for all soon! 