Skip to content

[6.5.0+] Regression when using EFCore [Entity] and Storage Actions in Saga #3342

Description

@dmalovric

Describe the bug
From version 6.5.0 onwards, sometimes saga handlers with [Entity] as parameters do not get executed unless (IsRequired = false) is specified.

Other times, the handlers will execute, but the [Entity] loaded will not be up-to-date, even though a previous handler updated it using Storage.Update.

I have verified that it works as expected in version 6.4.3, but not the very next one (6.5.0) nor any subsequent ones up to and including 6.16.0.

To Reproduce
WolverineRepro.zip
I have uploaded a repro which demonstrates the first case where the cascading message handler method is not executed.

Run the only Test in Tests/Tests. It checks for the presence of the final cascading message. It fails in 6.5.0+ but works in 6.4.3.

The second case was impossible for me to reproduce in a way that would demonstrate the issue but also not leak loads of my business logic, which would also only be a deterrent to finding the cause anyway.

The two seem related, so hopefully addressing one will address the other.

Expected behavior
Cascading handler methods should execute with the [Entity] injected and up-to-date.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions