Hello, Bruce, you've got my vote. And you could vote for your own idea too. Cheers!

By the way, I was thinking of "unique" as specific to an incident, so that if the same error occurred twice, then a different error number would be displayed to the user each time. I was imagining it that way because I don't know exactly what information SDL collects. Although the "generic error" might be the same for many incidents, other information collected about the user's Studio settings or system configuration might also be helpful for a specific incident.

Hi Daniel,

I completely agree with the "customer experience program" and thought this would be something relatively easy to piggy-back onto it.

Users in particular would find it easier to cite an error number instead of finding and sending an error stack.

It would also give users one more reason to participate in the program :-)

Best regards, Bruce

Hi  - actually repeatedly sending error info can be useful, as it allows us to identify more frequently vs. less frequently occurring issues in the field. We can use this to prioritise error fixing on our end. This is part of the "customer experience program". If you don't wish to send such error info to us, you can opt out via Help - Customer Feedback. Thanks, Daniel