Windows workflow 4.0 InstancePersistenceCommand Error

Question

I have a wcf workflow that have three receive activities arranged in a sequential manner. i.e

1.receive application 2. Manager1 approval 3. final manager approval my problem is that i am able to consume the workflow from my client application and call the first (receive application activity), however when i try to call the second (manager1 approval receive activity) i get the following error

The execution of an InstancePersistenceCommand was interrupted because the instance '16c3dae0-92f5-45e8-bdaf-d6f4051a0a39' has not yet been persisted to the instance store.

I have check the database (instance store table) and the record seems to exist. i have also setup Correlation as specified in this article Please help, this is urgent

score 5 · Answer 1 · edited Jan 25 '21 at 09:10

5

I finally figured out what was the problem. It has taken me three days.

I just needed to add the following:

<serviceBehaviors>
  <behavior>
    <workflowIdle timeToUnload="0"/>
  </behavior>
</serviceBehaviors>

You can get more details at this article.

NB: My workflow was getting the default timeToUnload value of 1 minute (from the machine config). Meaning when I called the next receive activity in my workflow, the workflow was still in memory. (really strange)

edited Jan 25 '21 at 09:10

peterh

11,875
18
85
108

answered Jan 11 '11 at 12:14

The workflow being in memory is no problem and only speeds things up. Or are you using a server farm and is the second request coming in on a different server? – Maurice Jan 12 '11 at 10:38

score 1 · Answer 2 · answered Jan 11 '11 at 07:05

1

Is the GUID the correct one? Sometimes the WF4 runtime will generate a new GUID if it can't find an existing one leading to some confusing error messages. Also changing namespaces brakes the correlation queries. So if you did that you need to recreate them, or go into the XAML, and fix them.

answered Jan 11 '11 at 07:05

Maurice

27,582
5
49
62

the Guid is the same as the one in the database – Jan 11 '11 at 08:20
what do you mean by "changing namespaces" – Jan 11 '11 at 08:48
Each SOAP service, and thus a WF service, use a namespace as part of its name. You can change these and that can cause issues. – Maurice Jan 12 '11 at 10:45

Windows workflow 4.0 InstancePersistenceCommand Error

2 Answers2

Linked