We have a workflow with several actions in a strong named assembly. While the workflow is awaiting user action, we are updating the assembly to a newer version. In the next step, the core of the workflow suddenly says that it can no longer find an instance of the workflow. This is literally about the build version number. If we do not change the version number, it will work. Additional exception information:
An instance of InstancePersistenceCommand named {urn: schemas-microsoft-com: System.Activities.Persistence / command} LoadWorkflowByInstanceKey was aborted by an error.
Error code name Instance is independent of .
Has anyone come across something like this?
source
share