Importing a very large number of saga audit snapshots with ID 00000000-0000-0000-0000-000000000000 can cause InvalidOperationException error

[ramonsmits]

Describe the bug

Endpoints that emit saga snapshots with incorrect sagas can emit snapshots with ID 00000000-0000-0000-0000-000000000000. Saga audit will store these without issues which eventually can result in:

Failed to execute reduce function on page #16445 (count: 90) Branch of 'SagaDetailsIndex' index. The relevant reduce result is going to be removed from the index as it would be incorrect due to encountered errors (reduce key hash: 18127671079156472777) Exception: System.InvalidOperationException: Tried to allocate 1.293 GBytes, which exceeds maximum allocation size of 1 GBytes

Solutions suggestion

1. Discard 00000000-0000-0000-0000-000000000000 snapshots with a warning message that developers should ensure their saga instances have a correct saga id

Related to:

• Do not emit saga snapshots with saga ID 00000000-0000-0000-0000-000000000000 NServiceBus.SagaAudit#412

[andreasohlund]

• Related issue Saga audit—completed sagas keep growing when the same correlation ID is re-used #3351