Hey @uckelman,
I believe this may have been fixed only in the last couple of weeks, so it looks like that was after your last update.
Can you try running the latest tag v3.6.0.beta1 which includes that fix?
Let us know if you’re still experiencing the issue or if it appears to be resolved.