Breaking changes in workflow_instances documents after upgrading from Elsa 3.2.3 to 3.3.5

[EstherWeintraub]

Hi,
I’ve recently upgraded from Elsa 3.2.3 to 3.3.5, and I’ve noticed that there are breaking changes in the workflow_instances documents in MongoDB.

Could you please advise on the best approach to handle these changes?
Is there a recommended migration path, script, or compatibility layer to bring existing documents in line with the new schema?

Thank you,

[sfmskywalker]

Hi @EstherWeintraub , can you share the details about the symptoms that you’re seeing? We always try to prevent breaking changes, but it sounds like we missed something during that release.

[EstherWeintraub]

Hi @sfmskywalker ,
In Elsa 3.2.3, the variable type was saved as:
"$type" : "Elsa.Workflows.Services.VariablesDictionary, Elsa.Workflows.Core",

In Elsa 3.3.5, this type has changed to:
"$type" : "Elsa.Workflows.VariablesDictionary, Elsa.Workflows.Core",

[EstherWeintraub]

[sfmskywalker]

Closing due to inactivity. We requested the failing document shape and symptoms, but no reproduction or follow-up was provided, so there is not enough evidence to recommend a safe MongoDB migration or data rewrite. If this is still relevant, please open a new discussion with the Elsa/MongoDB versions, a redacted before/after document, the exception or observed behavior, and a minimal reproduction.