For me too, but if I recall I couldn’t even set the header with a new conversation id. NServiceBus is actively fighting me on this, so I was ‘is there some bad practice that I’m missing’.
Thanks for raising an issue!
No. I’m using timer-triggered Azure Functions (which I think you should add as an alternative in the documentation :-). They work great!)
In this context, being scheduled is not important. I just wanted to explain the use case.
A scheduled Azure Function sends periodically a CheckForUpdatedContacts command to an NServiceBus endpoint. This endpoint handles the command by checking for updates and publishing ContactUpdated event for each updated contact.
The CheckForUpdatedContacts command is the start of the conversation, but all ContactUpdated events join this conversation. In this context the ContactUpdated event should start its own conversation, because I’m not interested in the check trigger.