Customer
Largest US-Based Healthcare
Description
Since most of you are relying on this new Categorization Mechanism, here is an issue we experienced while using it. For this client, we had enabled Germain’s Categorization for "Apex Unexpected Exceptions" using the logic outlined below:
However, after some time, the categorization IDs changed unexpectedly.
Cause of this issue & solution
The CategorizationDefinition was renamed by our Support Team in the middle of its use, which caused a new cache to be utilized, resulting in a new categorization ID. During our investigation, we discovered an issue in our Categorization/Correlation logic where a removed CategorizationDefinition was not prevented from being used. We addressed this bug in the past month.
Here are more details on Germain UX’s categorization feature.