The "Mark Exception" action automatically creates a tag if the Exception Reason is not empty. The automatically generated tag has the format: "Exception: {Exception Reason}".
The exception reason often contains case-specific data. E.g., "product 523462 could not be found.". Blue Prism then creates a tag from this exception reason, causing our BPATag table to grow indefinitely.
You could build your Exceptions to not have case-specific data in, but log the case-specific data immediately prior to the Exception occuring.
This way your BPATag table would not have a load of unique values, business users would see the high-level reason it was failing (and you could use this for high level metrics) and the developers could still check the logs for the specific reason for failure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
