Pages

Monday, June 4, 2012

Nintex Workflows: Good to know(1) - Dehydrating

After years of working with and teaching Nintex Workflows I made a list of important things that are not obvious, but serious Nintex designers should know. So here it is: A series of "Good to know" things about Nintex.

To start with I would like to write about Dehydrating!
Have you ever experienced the following:
You want to pause your workflow for 5 minutes, but instead it pauses longer than expected, maybe 7 or 10 minutes!
The workflow doesn't continue after a pause for action!



I made a simple workflow:
So it is not doing anything, but waiting for 5 minutes and writing a history entry.
More than 5 minutes later we look at the history:
Where is the custom log entry?





10 minutes later, but nothing happened!
When we use a activity like "Pause for" the workflow is dehydrating. Which means that it is going to sleep. It is no more stored in process memory, but in the database.
So how do we get it back running?

We go to Central Administration - Monitoring - Review job definitions and we search for the timer job called "Workflow". For this demo I disabled it. So now I am going to run it.
It will search for dehydrated workflows and. if required, start them.

Here we go!
The default value for the timer job is to start every 5 minutes. So that would mean, if we pause our workflow for 5 minutes that could be 10 minutes in the worst case.

That's it!

Please leave a comment if you have further questions.

No comments:

Post a Comment