Event definition cannot be published

[mmbb110]

We imported a package for transactional message and only first event and it's associated message was published but for the remaining we get the error

A transactional message associated with this event 'EVTPRO_' already exists, but with an incorrect delivery mapping. This event definition cannot be published.

We don't see any incorrect event or message mapping.

What could be the issue?

[SatheeskannaK]

Did you check anything with brand settings between the export/import environment causing this issue?

[mmbb110]

 for the first event the publication worked fine but when I tried for next it gives me the error described in my question.

I already have transactional message events linked to realtime, these new events are profile based. 

I don't need to do publication correct after importing my package?

[SatheeskannaK]

You can't have the same event id for both real-time and profile-based transactional configuration. You will have to unpublish and delete the events/message template before importing the events that are changed from real-time to profile and vice versa.

[mmbb110]

Yes, i do have the names for the events unique. Profile and realtime.

[SatheeskannaK · Accepted solution]

I was able to replicate the same error, where I created and published a profile-based transactional event (EVTtest123) on a staging environment and real-time based transactional event (EVTtest123) on a prod environment. Exported the event from the stage and successfully ported it to the prod environment. Prod environment transactional event updated from real-time to profile based after importing the package from the stage. When I try to publish the event in prod received the same error as you mentioned due to already having a real-time transactional event with the same name.