@seanbala We are aware of this issue and are working on a fix!