InstancePersistenceCommand Exception - Windows Workflow Foundation Issue

Moulshree Guleria 0 Reputation points

I am getting this exception when running the workflow, in my application logs-

The execution of an InstancePersistenceCommand was interrupted because the instance key {GUID} was not associated to an instance. This can occur because the instance or key has been cleaned up, or because the key is invalid. The key may be invalid if the message it was generated from was sent at the wrong time or contained incorrect correlation data.

When we check the Workflow data, we see that IsInitialized is 0 and it becomes a non-persisted instance. This is occuring when we are passing a large batch of requests to the workflow service at the same time, however it works fine for small batches (such as 10 requests). It is also only happening in our Production environment and is working fine in the lower environments with even larger batches. We wanted to understand why this issue occurs and what can be done to resolve this issue.

Any information on this would be really helpful, thank you!


Microsoft Technologies based on the .NET software framework.
3,472 questions
{count} votes