When an exception is raised by the Odata Adapter, there exists an attachment in the monitoring that offers a more comprehensive error description compared to the camel exception: ${exception.message}.
Is there a method to capture the details of the attachment within the exception subprocess?
