This issue is being actively investigated, and we do not currently have a workaround. I suggest trying again later in the week to allow time for a resolution.
