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
                            .WithKafkaKey<NotifyPaymentEvent>(envelope => envelope.Message.Id)

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=, 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)


Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:23 (14 by maintainers)

github_iconTop GitHub Comments

alefcarloscommented, Feb 24, 2023

@BEagle1984, @davimorao and I work together rs

We tried the beta and everything worked good!

@cookie-bytes did you try that?

BEagle1984commented, Feb 26, 2023

Published v4.1.1 including the fix

Read more comments on GitHub >

github_iconTop Results From Across the Web

Email stays in Outbox until manually send or receive
When you send an e-mail message in Microsoft Outlook, the message may remain in your Outbox folder as shown in the following figure....
Read more >
Email remains in Outbox if using DelegateSentItemsStyle
This article provides a resolution for the issue that the email message is still in Outbox when you use the DelegateSentItemsStyle registry ...
Read more >
Are the emails inside the outbox folder stored locally on ...
2 Answers. You're right. For IMAP accounts Outlook stores Outbox locally in . OST cache file.
Read more >
Messages get sent, but remains in outbox - MS Office
Messages are sent and the addressees receive them. However, the messages remain in my Outbox and are not moved to the Sent Items...
Read more >
Why an email gets stuck in Outlook and how to make it send
This article explains why an email message may be stuck in Outlook and how to fix this: make the message send or delete...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found