There was a known issue in ealier versions of 2.3.3, which includes 2.3.3.121, so that's the likely issue. Thread here:
Issue was resolve in 2.3.3.127. We're at full release on 2.3.3.135 at this point. Likely you'll have to update to resolve this - but I'd wait for @kkossev to confirm that your issue matches - I think that's what he thought it was.
