It’s a known issue of v3.8.5 which we’re currently investigating. One workaround is to downgrade to an older release.