I host workflow service on IIS and manage it with windows server appfabric.
I persist the instance with appfabric. There is a "Delay activity" in my WF service.
When it is delay.It will be persisted .In the appfabric dashborad I could find it in Persisted WF Instance ->Idel :1
Then I reboot my server. (Just want test reliability of appfabric).
I found the WF Instance status is still "Idel".But the workflow dose not complete as expected.
I found only I call another workflow service.The previous "Idle" Workflow instance will be continue.
How could I configure appfabric to automatically continue completing workflow service after server reboot?
It sounds like you are not using auto start. Is this correct?
Could you provide more information on what you did to start it? Is it just a matter of calling the service in your case?
If so, you could create a scheduled task to run on startup to call a script that executes a request to the service. Or you should use the auto start capabilities of AppFabric.
If this answers your question, please use the "Answer" button to say so | Ben Cline
Microsoft está realizando una encuesta en línea para comprender su opinión del sitio web de Msdn. Si decide participar, se le presentará la encuesta en línea cuando abandone el sitio web de Msdn.