I got an issue that involve my transactionnal message when trying to link a template I create with an event using SoapUI.
I already see another post on the forum but with no real answers on my issue.
So I first make a simple template and create an event name to specify the event type of the template and I publish the template with success.
I also send a proof with no problem.
I then make a SoapRequest such as this :
I got a success answer :
But still, when I check in the Adobe Campaign's event history, my events are not covered and the documentation doesn't help get through the problem.
I already check in the properties of the template to make sure the event name is correct and it's the case.
I also see that lots of people are facing this issue, do you have some answers for my problem ?
If you need more information, feel free to ask me !
Using Adobe Campaign v7 on Windows 10.
Usually when event status is "event not covered", it means MC routing phase didn't find any eligible template for your event. Please check that
you pushed the event with the proper operator
you have published your template
your template has the proper event type and the proper channel
Please go through below link to know more on this.
So I check all of what you ask and I'm facing another issue.
I push the event with the proper operator but go an error when pushing as see on those screens :
Then the publish of my template is good :
And in the properties, my template has the proper event type and the proper channel :
Maybe it's coming from the SoapUI request error when I try to log with the mc operator.
Any idea on that ? Thank you.
Also, I don't understand this part of the documentation concerning the screen with <batchEvent>
They say : Definition of the event type in the event properties.
Where can I find those event properties or should I make something with batch ? I am confuse with that.
Thank you for your answers !
Any idea on how to fix that "event not covered" issue or it maybe happened to someone recently ?
Perhaps a stupid question, but did you already add your event item in the dbEnum enumeration?
This step is done as well on the screen below :
Still have no idea on how to fix that, any more ideas ?
I still got the same issue on my SoapRequest even with that function name modification. (Too many arguments)
And the event not covered still remain.
Yes I notice that error and I change it already few days ago, sorry for not updating that.
it looks like that for now :
Or with the function change name :
The error in my SoapRequest for reminder :
Ajoute xmlEnvoyer, le paramètre que tu as ajouté en argument, au logInfo. Peut-être est-il vide.
Please check the value of xmlEnvoyer as parameter to logInfo, perhaps it is empty value.
Quand je rentre le xmlEnvoyer, il me renvoie un \n, qu'est ce que ca signifie ?
When i put the xmlEnvoyer, he gives me back a \n, what does that mean ?
Make sure you are sending the soap request with the same operator, using which you have connected your execution server with the control server. i.e mc.
So Firstly take a session token from mc user -
Then use this token within your request.
I was using the different operator then I got the same issue. But after that I tried with mc then issue is resolved.