Include additional information in Un-handled server exception along with Stack Trace

Thank You, Sheryl for your updates. I appreciate your effort for considering in the future roadmap.

Hi Raguram,

We have reviewed your enhancement suggestion.

Based on the information provided, our understanding of your request is as follows:

You are requesting that the content of the infrastructure messages that are logged when un-handled server exceptions occur be enhanced to include additional identification details such as Case ID to help identify and diagnose the issues that have occurred.

The theme is aligned with our current strategy for our product and we have accepted your suggestion as a consideration for a future release.

Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

Regards,
Sheryl Brenton, SPM Product Management Team

Hi Sheryl Brenton,

Good morning. I just wanted to follow up to check whether you have any updates. Please let me know if you are looking for any additional information.

Thanks,

Ragu.

Hi Raguram,

Thank you for providing the additional information requested. Within the next 30 days we will review the details you have provided and inform you of our analysis and decision.

Regards,
Sheryl Brenton, SPM Product Management team

Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
Additional details can be found here.

Here are the attachments.

Thanks,

Raguram.

Thank You, Sheryl for your continuing investigation.

• The 'Outcome Plan' stacktrace was shared as an example. We certainly build a business logic and implement a custom message to handle it better. However, if the un-handled server error shares the respective ID, it would be easier for the developer to identify the respective case and business scenario to recreate and fix the issue.

• For your further analysis, I've attached various UHSE full stack trace from different functionalities. Please go over these and let me know if you are looking for additional information.

Thanks,

Raguram.

Hi Raguram,

Thank you for the responses to our questions and the two examples you provided.

We have some follow-up questions and requests.

We would like to better understand the Outcome Plan related stack trace example you provided in "664002BZ3G added attachment, UHSE_OutcomePlan.txt".
When reading back the context panel details for this screen, do you always expect that Outcome Plan be present and if so, why is it not? If the record may or may not be there, that scenario is usually handled by writing business logic to handle the RecordNotFoundException and produce a more user friendly message or log the more specific details into the logs at that layer.

There isn't enough of the exception trace present in the other example for us to try and understand what might be the cause and possible resolution to this Un-handled server exception.

In general, these types of UHSEs should not be happening in the product and we would like to see more examples of these exceptions (with the full stack trace included) if you could provide them, in order to see if we can begin to identify patterns and better understand what further help the system could give to help you to diagnose them.

The Outcome Plan example appears related to a customization you have made. Are there any examples you could also provide that you feel are UHSEs being caused by OOTB functionality?

Also, any examples from the three areas you provided where the majority of the UHSE's are occurring would be useful:
56,815 (~39%) exceptions were thrown for ‘DPEnactment’.
22,874 (~16) exceptions were thrown for ‘PerformDeferredRecalculationsFromPrecedentChangeSet’.
13,039 (~9%) exceptions were thrown for ‘DelyadEligibilityAssessment.reassessCase’.

Regards,
Sheryl Brenton, SPM Product Management team

Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
Additional details can be found here.

Hi Raguram,

Thank you for providing the additional information requested. Within the next 30 days we will review the details you have provided and inform you of our analysis and decision.

Thank you,
Sheryl Brenton, SPM Product Management team
Note: We have improved your RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
Additional details can be found here.

Hi Sheryl Brenton,

Thank you for your time taking to review and provide the updates. Please see my response for your questions.

1. As per the analysis performed for the last two weeks (01/24 to 02/04), In total, there were around 145,291 ‘Un-Handled’ server exceptions and the majority of errors were from the following.

• 56,815 (~39%) exceptions were thrown for ‘DPEnactment’.

• 22,874 (~16) exceptions were thrown for ‘PerformDeferredRecalculationsFromPrecedentChangeSet’.

• 13,039 (~9%) exceptions were thrown for ‘DelyadEligibilityAssessment.reassessCase’.

2. For your reference, I have attached two exception logs. When we look at these exceptions from the server logs, we may not be able to track back as it doesn’t give any reference from where (case, participant, or any record ) the exception was thrown. Thus, it would be better if the exception includes additional key related information such as caseID, concernRoleID, outcomePlanID or the unique key to easily identify the source record and fix the respective problems.

This would help to minimize the number of UHSE produced per day. Please let us know if you are looking for additional information.

Thanks,

Raguram.

Hi,

We would like to gather further information from you related to this enhancement request.

1. Are there particular areas of the application which are proving problematic and have you determined that this is a usage problem rather than an OOTB SPM product issue?
2. Would it be possible for you to provide a few examples of such errors? The PII data can be removed from the examples, it is just to get a sense of what type of errors you are referring to and where they are originating from within the application.

Please provide the requested information within 30 days so we may proceed with our evaluation. If we do not hear from you within that timeframe we will have to close the request due to insufficient information.

Thank you,
Sheryl Brenton, SPM Product Management team

Note: We have improved the RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
Additional details can be found here.

Hi,

Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

We will review the information you have provided and get back to you within 30 days. If additional details are required in order to complete our evaluation, we will send you a request for more information.

Thank you,
Eloise O'Riordan, SPM Product Management team

Note: We have improved the RFE experience and transitioned to an Ideas Portal provided by our trusted business partner Aha!
Additional details can be found here.