No handlers could be found for message type: Document.Messages.DocumentSubmitted1

Hi,

I have four endpoints running with the below configurations.

Transport - Azure service bus
Persistence - Azure Cosmos DB

I am publishing an event DocumentSubmitted1 from an endpoint and the handler is in another endpoint. The Endpoint has a handler not throwing any exception but the remaining endpoints are throwing the below exception. Any help is highly appreciated

System.InvalidOperationException: No handlers could be found for message type: Document.Messages.DocumentSubmitted1
at NServiceBus.LoadHandlersConnector.Invoke(IIncomingLogicalMessageContext context, Func2 stage) in /_/src/NServiceBus.Core/Pipeline/Incoming/LoadHandlersConnector.cs:line 57 at NServiceBus.Persistence.CosmosDB.CurrentSharedTransactionalBatchBehavior.Invoke(IIncomingLogicalMessageContext context, Func2 next) in //src/NServiceBus.Persistence.CosmosDB/SynchronizedStorage/CurrentSharedTransactionalBatchBehavior.cs:line 18
at NServiceBus.ScheduledTaskHandlingBehavior.Invoke(IIncomingLogicalMessageContext context, Func2 next) in /_/src/NServiceBus.Core/Scheduling/ScheduledTaskHandlingBehavior.cs:line 22 at NServiceBus.DeserializeMessageConnector.Invoke(IIncomingPhysicalMessageContext context, Func2 stage) in /
/src/NServiceBus.Core/Pipeline/Incoming/DeserializeMessageConnector.cs:line 33
at NServiceBus.InvokeAuditPipelineBehavior.Invoke(IIncomingPhysicalMessageContext context, Func2 next) in /_/src/NServiceBus.Core/Audit/InvokeAuditPipelineBehavior.cs:line 20 at NServiceBus.ProcessingStatisticsBehavior.Invoke(IIncomingPhysicalMessageContext context, Func2 next) in //src/NServiceBus.Core/Performance/Statistics/ProcessingStatisticsBehavior.cs:line 25
at NServiceBus.TransportReceiveToPhysicalMessageConnector.Invoke(ITransportReceiveContext context, Func2 next) in /_/src/NServiceBus.Core/Pipeline/Incoming/TransportReceiveToPhysicalMessageConnector.cs:line 39 at NServiceBus.RetryAcknowledgementBehavior.Invoke(ITransportReceiveContext context, Func2 next) in /
/src/NServiceBus.Core/ServicePlatform/Retries/RetryAcknowledgementBehavior.cs:line 27
at NServiceBus.MainPipelineExecutor.Invoke(MessageContext messageContext) in /_/src/NServiceBus.Core/Pipeline/MainPipelineExecutor.cs:line 35
at NServiceBus.Transport.AzureServiceBus.MessagePump.InnerProcessMessage(Task`1 receiveTask)
Exception details:
Message ID: 2410b8f5-d53d-4cb1-938b-adaa00597bd5
Transport message ID: 38a0d1e5-7798-43af-9fca-6f627ac93c8d

Thanks, Pon

Found the issue. There is an existing Event DocumentSubmitted and the new event created is DocumentSubmitted1. The subscription rule is defined as [NServiceBus.EnclosedMessageTypes] LIKE ‘%Document.Messages.DocumentSubmitted%’ . That is the reason the new ones looking for it. Once I change the name to make this condition false it’s started working. I am a bit worried about this, is there a way to avoid this?