Apologies for the delayed response. This is a known issue, but please see here for a workaround in the mean time.