The fix for the issue described here isn’t in the main-line 8.0.7 yet - 8.0.6 has it fixed in the final release, but the changes won’t be merged into 8.0.7 until after that release actually happens. There shouldn’t be any way for the setting to be acting like that besides that schema upgrade firing, so I’m going to say it’ll be fixed once everything’s brought up to date - but we’ll definitely keep an eye on it and do more testing.
1 Like