We are aware of this issue and we recognise how problematic it is. Could you try our workaround here?: