Should you send that Error Report?

Don't suffer in silence - send the error report to Pronamics

Will you choose to suffer in silence?

You hit a button in your application and something breaks. You curse, then a pop up appears asking if we wish to send an error report.
We get it – you just want to get on with your day.
You hit no. It’s the easiest decision, after all—no consequences, no further commitment. You’re smart—you’ll work around the issue and get on with the job. Then the error happens again, and you get frustrated at the program for not doing the thing you asked it to.
What if you do send that error report?
Expert Estimation and Expert Project capture no sensitive data, so by sending an error report you are helping to improve the very product that you are using, to make it better to use in the future. That helps everyone!
So what actually happens when you hit “Send”?
Depending on whether you click Send Error Report or Email Report, Pronamics receives an email via our support@pronamics.com.au inbox, or we receive a ticket in our issue tracking system with a snapshot of the error message and the time it occurred. It might also contain the version of the program you are running. Sometimes we have already released an update that fixes the error you are seeing!
No confidential data is passed on to us
We might receive information about what the code was doing at the time of the error, but we can’t see what you were typing, so don’t stress!
If we can diagnose the cause of the issue straight away you’ll receive a phone call from a Pronamics Support Team member with an answer. Sometimes we need more information on the process you were attempting, so we’ll still call, and if we can resolve the issue for you on the spot, we will.
If we can’t fix it right away, we’ll still tackle the issue.
Sending error reports gives our developers information so they can drill into the code. It’s entirely possible that other users are experiencing the same issue, so reporting means that tickets can be prioritised efficiently and we can commit resources to improving the software.
So send that error report.
The squeaky wheel gets the grease, but more importantly you get answers and a better product, faster. That means you get more done, faster.

Will you choose to suffer in silence?

You hit a button in your application and something breaks. You curse, then a pop up appears asking if we wish to send an error report.
We get it – you just want to get on with your day.
You hit no. It’s the easiest decision, after all—no consequences, no further commitment. You’re smart—you’ll work around the issue and get on with the job. Then the error happens again, and you get frustrated at the program for not doing the thing you asked it to.
What if you do send that error report?
Expert Estimation and Expert Project capture no sensitive data, so by sending an error report you are helping to improve the very product that you are using, to make it better to use in the future. That helps everyone!
So what actually happens when you hit “Send”?
Depending on whether you click Send Error Report or Email Report, Pronamics receives an email via our support@pronamics.com.au inbox, or we receive a ticket in our issue tracking system with a snapshot of the error message and the time it occurred.
It might also contain the version of the program you are running. Sometimes we have already released an update that fixes the error you are seeing!
No confidential data is passed on to us
We might receive information about what the code was doing at the time of the error, but we can’t see what you were typing, so don’t stress!
If we can diagnose the cause of the issue straight away you’ll receive a phone call from a Pronamics Support Team member with an answer. Sometimes we need more information on the process you were attempting, so we’ll still call, and if we can resolve the issue for you on the spot, we will.
If we can’t fix it right away, we’ll still tackle the issue.
Sending error reports gives our developers information so they can drill into the code. It’s entirely possible that other users are experiencing the same issue, so reporting means that tickets can be prioritised efficiently and we can commit resources to improving the software. So send that error report. The squeaky wheel gets the grease, but more importantly you get answers and a better product, faster. That means you get more done, faster.