We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug WorkflowCore 3.13.0 WorkflowCore.QueueProviders.SqlServer 3.13.0 WorkflowCore.Persistence.SqlServer 3.13.0
Our SQL Server db size increased nearly 30 times in one day (from some MB to 5 GB).
This are the stats of our current DB:
Regarding the queues: The only queue containing items is "//workflow-core/workflowQueue" with 2k entries.
The only thing I discovered is that there are 6mio conversations (Is this normal?).
To Reproduce
Expected behavior Consistent database size that is not increasing if nothing happens (or at least not 33 times)
UPDATE: After deleting them with END CONVERSATION xxx WITH CLEANUP, and shrinking the db, it got back to its normal size.
END CONVERSATION xxx WITH CLEANUP
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
WorkflowCore 3.13.0
WorkflowCore.QueueProviders.SqlServer 3.13.0
WorkflowCore.Persistence.SqlServer 3.13.0
Our SQL Server db size increased nearly 30 times in one day (from some MB to 5 GB).
This are the stats of our current DB:
Regarding the queues: The only queue containing items is "//workflow-core/workflowQueue" with 2k entries.
The only thing I discovered is that there are 6mio conversations (Is this normal?).
To Reproduce
Expected behavior
Consistent database size that is not increasing if nothing happens (or at least not 33 times)
UPDATE: After deleting them with
END CONVERSATION xxx WITH CLEANUP
, and shrinking the db, it got back to its normal size.The text was updated successfully, but these errors were encountered: