You must ensure that the technical workflows on the control instance and the different execution instances have indeed been created and started before deploying any transactional message templates.
The various technical workflows related to transactional messaging (Message Center) are broken down between the control instance and the execution instance(s).
On the control instance, whether you have one or several execution instances registered, you must create one archiving workflow for each Message Center execution instance external account. Click the Create the archiving workflow button to create and start the workflow.
These workflows can then be accessed from the Administration > Production > Message Center folder. Once created, the archiving workflows are automatically started.
On the execution instance(s), the technical workflows for transactional messaging can be accessed from the Administration > Production > Message Center folder. You just have to start them. The workflows in the list are:
Processing batch events (internal name: batchEventsProcessing ): this workflow lets you break down batch events in a queue before they are linked to a message template.
Processing real time events (internal name: rtEventsProcessing ): this workflow lets you break down real time events in a queue before they are linked to a message template.
Update event status (internal name: updateEventStatus ): this workflow lets you attribute a status to the event.
The following event statuses are available: