![\"Workflow](\"http:\/\/www.stuartroberts.net\/wp-content\/uploads\/2010\/10\/Workflow-Timer-Job.jpg\" "\\"Workflow")
<\/a>\nWorkflow Timer Job Setting<\/strong><\/span><\/p>\n
Some other posts mention running the stsadm command: This lets you check if the workflow job is configured. I have the feeling this is only relevant for SharePoint 2007 in combination with this hotfix<\/a>.<\/p>\n In my environment, using 2010, I ran the above command and got the Property Exits=”No” <\/em>message, which indicates that it’s not been configured. There’s no need to set this property, as the delay activity does eventually fire once the Workflow timer job kicks in.<\/p>\n If you need the delay activity to fire more frequently than the default five minutes, you’ll need to update the schedule for the Workflow timer job to run more frequently.<\/p>\n If you’re trying to debug a workflow or custom activity and are using the Delay activity you will need to connect to the w3wp (for the web application running the workflow) and owstimer processes. Otherwise, you’ll only be able to debug the workflow as it initiates and not for the steps you have configured after the delay.<\/p>\n","protected":false},"excerpt":{"rendered":" Trying to use the Delay Activity workflow activity in a SharePoint workflow and having problems with it firing? For SharePoint 2010, the delay activity will only be checked if it has completed the configured delay every time the Workflow timer … Continue reading
\n
\nstsadm -o getproperty -propertyname \u201cjob-workflow\u201d -url http:\/\/localhost<\/em><\/p>\n