The most recent where there is not already a Jira issue was on the 7th October, this was because the local item status is unavailable which we do not handle, have not created an issue for this yet.

This probably should be an epic to which stories are assigned which fall under this scenario, probably need a trackingFailedOverview script similar to the errorOverview script that gives a breakdown of all the tracking failures, how many times they occur and when the last instance was.

The tracking failures are less serious as they do not take the request into an ERROR state, but it could mean the request is continually tracked as it may never change state depending on the nature of the failure

• are there any recent incidents of this?

• do the changes to stacktrace help?

Update:

I have refactored the way in which the audit saves the stacktrace which may help with investigating issues. The commit can be found here:

The stacktrace being output by that commit is not very useful, as it is just adding "StackTrace": "[Ljava.lang.StackTraceElement;@4749162f", since that dosn’t really tell you anything apart from the fact it is a list of type Stacktrace, ideally we would have something more useful that just kept the lines in the java, org.olf.dcb and services.k_int namespaces as anything else is not really that useful for determining where the problem is.

when this occurs we do not have the stacktrace in either the log file or audit trail, this needs to be added so we know where the problem lies.

does this commit address the stacktrace gap? If so, is there some additional action needed for this ticket, or is it just about adding more logging for better future diagnostics?