Workflow is slow to open

[Migration User]

After deploying my newly built workflow to altiris as a help desk item, the workflow is very slow in opening.  After waiting forever (it seems) the workflow runs as intended and any subsiquent time there after it open and runs quickly until the next day . I have to fire it off once again and wait for it to run. What am i missing.

[matzebru]

I had some slowness in one of my published projects and there are a couple of things I could suggest to look at.

• If the problem is slowness without errors, try AKB 47110:Workflow project running slow after published to server .
• If you are getting out of memory errors, take a look at AKB 47301:Workflow project slows down when running multiple tasks .
• One other thing that could be causing it, and I don't believe this is in the Knowledgebase, is if you have "Wait" components in your Workflow project. I was having slowness in a Workflow project and debugging wasn't the issue so one of the Workflow Engineers at Symantec had me uncheck "Check Passive Completion" under the "Passive Merging" tab of Wait components I had and that took care of the slowness.

If anyone has any other solutions for slowness, please post them! Thanks

[Migration User]

One more quick thing to check: on the Publishing tab of the project properties, make sure Auto Initialize is checked before publishing. Unsure if the KBs mention this.

[matzebru]

Auto Initialize isn't checked by default when I open a new project and I couldn't find any reference to it in the Workflow Admin or User guides. Could you tell us what the Auto Initialize does specifically? Thanks!

[Migration User]

Auto Initialize, in a sense, "preloads" your project in the workflow engine. It's probably not on by default for the reason of having multiple WFs "preloaded" on a server could be pretty memory-intensive.

[matzebru]

Thanks for the explanation reecardo!

[Steve Wayment]

My logs are being flooded with errors from two specific workflows.  It seems that these workflows have current processes dating back 5 or 6 months.  It looks like the user closed the browser without finishing the workflow, and the timeout functions are not working.  The log file says "Object Reference not set to an instance of an object" when attempting to follow the timeout path.  But I don't have anything between Timout and End. I have tried aborting these processes manually, but it just takes me back to the main page without actually aborting.  I even completely removed the project and re-deployed it, but the processes are still there.  Any ideas how to remove these, and what might be causing the timout errors?

[Migration User]

You deleted the projects from IIS?