If you make a call through postman or any other tool, you will get some identifier in response.
<SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns="http://xml.apache.org/xml-soap" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<urn:PushEventResponse SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:urn="urn:nms:rtEvent">
<plId xsi:type="xsd:long">72057594037935966</plId>
</urn:PushEventResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>With Adobe support's help, you can check the actual reason for the delivery failure on the execution instance.
https://experienceleague.adobe.com/docs/campaign-classic/using/transactional-messaging/processing/event-description.html?lang=en
@thibaultb473199 wrote:
Hello @jyoti_yadav thank you for your reply. Unfortunately, I don't find any "delivery" tab as you can see on this screenshot. 
The issue of this real time is that it's in pending mode and when reach the time of the sending, goes back to pending mode over and over until it reaches 32 errors. I can't see any way of finding any error.
Is there another way to find such error ?
Thanks in advance
@thibaultb473199 wrote:
Hello @jyoti_yadav thank you for your reply. Unfortunately, I don't find any "delivery" tab as you can see on this screenshot. 
The issue of this real time is that it's in pending mode and when reach the time of the sending, goes back to pending mode over and over until it reaches 32 errors. I can't see any way of finding any error.
Is there another way to find such error ?
Thanks in advance