Note that there are some explanatory texts on larger screens.

plurals
  1. PONServiceBus Saga can't find handler because it's using the wrong ID
    primarykey
    data
    text
    <p>I am using NSB 4. I have a saga that has the following </p> <pre><code>BaseSaga&lt;OrderSagaData&gt;, IAmStartedByMessages&lt;OrderMessage&gt;, IHandleMessages&lt;VendorCreatedMessage&gt;, .... </code></pre> <p>BasSaga just wraps saga. I don't know why I've got bigger fish to fry right now.</p> <p>I then have </p> <pre><code>public override void ConfigureHowToFindSaga() { ConfigureMapping&lt;VendorCreatedMessage&gt;(m =&gt; m.SagaId).ToSaga(s =&gt; s.Id); </code></pre> <p>my OrderSagaData looks like this</p> <pre><code>[Serializable] public class OrderSagaData : IContainSagaData { [Unique] public virtual Guid Id { get; set; } public virtual Guid MessageId { get; set; } </code></pre> <p>VendorCreatedMessage</p> <pre><code>[Serializable] public class VendorCreatedMessage { public Guid SagaId { get; set; } public Guid MessageId { get; set; } </code></pre> <p>Then finally in my logs I get </p> <p>Could not find a saga for the message type Messages.Vendors.VendorCreatedMessage with id 7af7dff2-bf03-4ebd-9e6c-a27a01125ceb. Going to invoke SagaNotFoundHandlers. </p> <p>The message is the correct namespace and all, but the id (7af7) is not only the wrong id but I can't find it anywhere else. It's not in the vendor service logs or in the saga logs. When I look at the queue the vendor service is sending the correct SagaId.</p> <p>I'm very confused and don't know where it's getting strange (7af7) id or why it's not using the proper sagaid.</p> <p>Any help would be appreciated.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload