Hello,

we have trigger based Journeys created in the last few days where we see that there are a lot of data in the "Exit reasons" "Unmet trigger condition". I saw that there is a new feature generaly available (Real-time tile analytics in journeys). I understand that it should help to investigate why data exited the journey. But for triggers like "statecode" its a huge mess. Your own documentation regarding dataverse triggers in journeys (https://learn.microsoft.com/en-us/dynamics365/customer-insights/journeys/real-time-marketing-dataverse-trigger) mention that filters should be used for fields like statecode. We did it like that and it worked fine until the new functionality got active by default. Now we have thousands of "Unmet trigger condition" cause it make an entry each time the statecode change. Even if we filter for e.g. statecode equals completed.

Please remove the counting of "unmet trigger criterias" from the exit reasons.