Comment 15 for bug 1771075

Good news - I got the chance to test this in our production environment today for about 7 hours and no issues whatsoever. Given that this workload was triggering the issue pretty reliably within about half an hour before, I think this fix has done the trick. Thanks a bunch for your help!

What are the next steps here?