That does seem really, really strange.
Does the same thing happen if you start the process using the regular start process by key rest call rather than via the message api?
Turns out that you’ve got a space in the Initiator field. This then creates a variable with with the username of the initiator of the process instance. in your case it’s done via message so the value is null.
If you remove the space the variable shouldn’t appear.
Hi @aravindhrs
It is written “The attribute specifies a process variable in which the user id of the process initiator is set.”
So if I understand correctly the Camunda engine will set this field automatically when the process is started by a given user, but in case of Message start event I must set this field “manually”?
If a process is started with an authenticated user, ie. if you are logged in in the tasklist, initiator of the process instances should be set. You can get it either by the Java API or the REST API.
In case of message start event, for initiator you can refer the process variable which is sent from the message payload.