Hey all - I just wanted to confirm that our tentative fix for this behavior shipped with the release of version 3.198.0! It may not address everything described above, but should hopefully be a significant improvement. We'll keep an eye on our logs, but don't hesitate to reach out here if you see anything worth flagging!
2 Likes