1.22 is going to have a pretty major rewrite of how all of that works which might fix this issue. Do you see the same behavior on this version: