Hi again folks - while we’re investigating this issue, there is a possible workaround described here: