Skip to content

Event subscriptions not persisted to database #1192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
slogsdon7 opened this issue Jul 24, 2023 · 0 comments
Open

Event subscriptions not persisted to database #1192

slogsdon7 opened this issue Jul 24, 2023 · 0 comments

Comments

@slogsdon7
Copy link

slogsdon7 commented Jul 24, 2023

Describe the bug
Recently we had three Workflows that started with WaitFor steps not proceed after the corresponding events were published. After restoring a database snapshot to one before the events were published and querying the WFC tables we were able to determine that the event subscriptions were never persisted to the database.

To Reproduce
Steps to reproduce the behavior:
I have not managed to reproduced this error.

Expected behavior
Subscriptions should be persisted to the database.

Additional context

  • Using SqlServer for persistence
  • WFC version is 3.8.1 on .NET 6
  • The three Workflows started at nearly the same time
  • No errors in the logs to indicate any issues persisting the data
  • Suspect it may be related to issues supposedly fixed by Fix race condition on stop #1081, though we don't see any logs that say the service is stopping until about 30 minutes after the Workflows were started (This being caused by an idle timeout which we are going to disable).

If there is any additional information we can provide please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant