Glad to hear it’s back! And nice catch on figuring out the issue. We have an open ticket for that bug (since 8.0.33).