Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Outbox messages are store with defferent "EndpointName" and "ActualEndpointName"

See original GitHub issue

I expect “ActualEndpointName” equals “EndpointName” in the outbox table, but it’s defferent (see screanschort).

Here outbound configuration

                        .AddOutbound<NotifyPaymentEvent>(endpoint => endpoint
                            .ProduceTo(nameof(NotifyPaymentEvent))
                            .WithKafkaKey<NotifyPaymentEvent>(envelope => envelope.Message.Id)
                            .Configure(producerConfig)
                            .SerializeAsJsonUsingNewtonsoft()
                            .ProduceToOutbox())

This seems to be the cause of the error:

fail: Silverback.Messaging.Outbound.TransactionalOutbox.OutboxWorker[1077]
      Failed to produce the message stored in the outbox. | endpointName: StudentUserPhoneDuplicateEvent, messageType: *project-name*.DrivingStartingEvent, *project-name*, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null, messageId: 1e563aad-8b99-4daa-a981-f667d507bb8a, unused1: (null), unused2: (null)
      System.InvalidOperationException: No endpoint with name 'StudentUserPhoneDuplicateEvent' could be found for a message of type '*project-name*.DrivingStartingEvent'.
         at Silverback.Messaging.Outbound.TransactionalOutbox.OutboxWorker.GetTargetEndpoint(Type messageType, String endpointName, IServiceProvider serviceProvider)
         at Silverback.Messaging.Outbound.TransactionalOutbox.OutboxWorker.ProcessMessageAsync(OutboxStoredMessage message, ConcurrentBag`1 failedMessages, IOutboxReader outboxReader, IServiceProvider serviceProvider)