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?
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.
It is strange, the error still mentions the nms:rtEvent instead of your cus method.
Please add xmlEnvoyer in your logInfo in order to debug
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.
\n is new line
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.