It sounds like a known bug in the audience manager, which, unfortunately, is still not possible to reproduce, and therefore there is still no correction. There is a temporary solution (requiring manual changes to the database), so you should contact support.
BluePrint, , . - , "", , - .
, , , ; ...