@JohnSnow We haven't been able to replicate the issue nor find a reason this is happening. Are you still seeing this?