Please see the attached document for the current workaround while our development teams are actively working on the identified issue.