LocalExplainer's handle the provision of different explanations for a decision.

• They are available at both message queue and REST endpoints.

• Their execution is synchronous, i.e. the request is received, the explanation is processed and a result returned.

With particular regard to their invocation from a message queue is that the incoming message is only ACK'ed after the explanation processing has completed. In some circumstances this could be after the message queue has timed-out the message ACK.

We need to decided how best to handle this.

Increasing the timeout of a message ACK is a workaround that could lead to resource depletion on the backend (server, POD etc) as the messaging system needs to keep resources available for longer.

If we ACK messages before execution of an explanation is complete we could loose messages if, for example, the explanation throws a runtime exception before completing and returning results.