We have experienced that expressions with audience names in the expression is not updating if the audience is changing name. This causes the expression to fail. since the audience "is no longer there". This causes problems for the users of the platform and the customers receiving communication.
In bigger organizations like ours there are many different teams working in AJO at the same time, also in different countries. If there is an audience library to be used of many users, as part of staying under the audience threshold limitation, many user can use the same audience for different kind of activities. Both as inclusions, as well as exclusions in the organizations activities. And many will therefor also have the same audiences used in expressions.
We see that this now causes big and surveil danger in using expressions in AJO Journeys. An audience name can easy be changed, planned or by mistake. And the consequences can be big when expressions then stop to work as planned, only because of a name change. The changer of the name might not even be ware of all the Journeys where this audience name is been used. Backtracking this can be a though and hard job, finding all the logical breaks that now has has come.
We suggest that there is "another" connector in the expression builder that uses the ID for the audience rather than the name. Relaying on a name is not a good idea in general. You can showing the name in the creator, but in the back is should really be an ID that is used, something stable and reliable that doesn't change regardless of name and content of the audience.
This discovered weakness can cause surveil damage to our customers, without anyone knowing.
