• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 909
  • Last Modified:

WF: State Machine Persistence WorkFlow


I need some design help.

I have a state machine that I need to restart when the workflow is done. I do not need to save the current states (pause the state machine) just rerun it from the start.

why I need this is becase the load of a new instance takes to long so I need to build the sate machine and when a user press start I need it to execute the state machine  directly without any delay of creating a new instanceand and when the user press start again I want to rerun it, and so on.

How do I do this?

Must I use the SqlWorkflowPersistenceService even if  I just want to restart it from the beginning? Or is there a easyer way to do it then?
1 Solution
Workflows are not designed to do this and it will give you all kinds of problems. You could however build a form of cache pool with a limited amount of new workflows waiting to be used. Everytime a new workflow is taken from the cache pool, you can asynchronisally put a new workflow into the pool to ensure that the pool does not end up without any prepared workflows.

It's a bit like a queueing mechanism or a car plant. Workflows are never fast and will always have a delay. There is no way to fix this, as this is by nature in any kind of workflow in any system. It's just the users perception which is the problem.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now