Highlighted

Soap call using Message center

vendimb15716755

28-09-2017

HI

I am trying to use the SOAP UI to test the message center email. The soap call goes fine and I get back the Id from the event when I test .there is no email going out and the events are marked as Pending. Any Idea what I am missing? When I test the template to send proof it works fine

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:nms:rtEvent">

   <soapenv:Header/>

   <soapenv:Body>

      <urn:PushEvent>

         <urn:sessiontoken>___7cedba79-c6ad-43c9-a367-5c228b698035</urn:sessiontoken>

         <urn:domEvent>

        

       <rtEvent xmlns=""  type="tstThankYouForRegisteringRecipient" email="test@gmail.com"

wishedChannel="email" externalId="1234">

<ctx>

        <website name="ecomerce" url="http:www.gmail.com"/>

        <customer email="test@gmail.com" firstName="test" lastName="test"/>

      </ctx>

      </rtEvent>

</urn:domEvent>

      </urn:PushEvent>

   </soapenv:Body>

</soapenv:Envelope>

Replies

Highlighted

Vapsy

Employee

28-09-2017

If the event is in Pending status it means that they have not been connected with their associated template to launch a delivery or there is some issue.

First point will be to check if rtEventProcessing technical workflow is running without errors on the execution instance.

Can you please check that.

When you send a proof it is executed on the control instance while API calls go to execution instance and hence the two are not related.

Highlighted

joanag55068639

29-09-2017

Hi

I think that you have some issue on RT instance (the server of Message Center who sends the transactional message). It could be a deliverability issue (SMTP server of message center hasn't the necessary rules).

Regards.

Highlighted

vendimb15716755

29-09-2017

Thanks Vipul

based on my SOAP call do you see any issues? Does the template that I call need to be published before testing?

not sure what this mean:

"If the event is in Pending status it means that they have not been connected with their associated template to launch a delivery or there is some issue."

thanks

Highlighted

Vapsy

Employee

29-09-2017

Is you Control and Execution instance on the same installation or they are instances.

Templates are created using the Control instance and they need to be published on Execution instance before firing the relevant API call on the execution instance. If you have not published it, execution instance will not fire an email for the API call.

First thing to check after that is whether or not the rtEventProcessing workflow is running properly.

Highlighted

vendimb15716755

29-09-2017

I started the workflow and that is running properly. Now I am getting event not covered and there is not much on the logs. I tried with template that is published already and getting the same issue

Highlighted

Vapsy

Employee

29-09-2017

Event not covered means that there is no template on the execution instance which is connected to event type tstThankYouForRegisteringRecipient

Can you please check the execution instance.

Highlighted

vendimb15716755

04-10-2017

HI

There was an issue with Execution center which its fixed now and I was able to publish the template. I am still getting the same error from the soap ( event not covered)

the technical workflows are running so not sure where the issue is?

Please help if you can

Highlighted

vendimb15716755

05-10-2017

Hi Vipul

When you say there is no Template on the execution instance how you check that in Cloud? if the template is published successfully doesnt that mean that it should be on the execution instance?

any direction would be appreciated

thanks in advance

Highlighted

Vapsy

Employee

05-10-2017

Hi vendimb15716755 ,

I'm a bit confused now. From your previous update it appears you do not have access to execution instance (as it is in Cloud) and hence you cannot check the template on the execution side.

However, over your previous few updates, you have confirmed you could see that the technical workflows are running fine. Where did you check their status?

I would ask you to reach out to Adobe Support if the instances are Adobe hosted as they can use their login to verify what is wrong.

Regards,
Vipul