We have the following situation at our Customer LichtBlick SE. The customer resumes messages based on the URI. So they must know what is the end system to decide if the message will be resumed or not. That works well. But now we are implementing a FIFO pattern with ODX possibilities so if a ODX breaks this will be suspended and all messages too. But we do not see the URI on the suspended messages even if we set transport location and transport type in the context. So our customer cannot decide which messages shall be resumed. If there a way to use custom promoted properties in this way, so we can set them to some values or you can show the URI. Is there an easy way to put the error description on the grind like the error code? Error code is not really helpful.

• Idea shared by Milen Koychev.