I gave it one last go with support, and it has been determined that this is an issue that others have now reported experiencing, so got it 'ticketed' and will be corrected with a future update
