Based on IAmStartedByMessage should require a mapping · Issue #2442 · Particular/NServiceBus · GitHub, it seems that all messages need a mapping in ConfigureHowToFindSaga. This includes starting messages.
My starting messages will always create new sagas, and actually don’t include any properties in the message that are even capable of finding an existing saga.
I currently need to add a dummy property to my starting messages, and add a dummy mapping that will never match an existing saga.
This does work around the issue, however, every time a starting message comes in, nservicebus queries Azure Table Storage to see if the saga exists (which obviously it never does).
This is causing 404s to appear in application insights.
Why am I forced to create a mapping on a starting message? And is there any way to prevent nservicebus from trying to look up a saga that will never exist?