I want to pause a workflow for 6 weeks. After that duration it checks a specific list for an item and sends an email when found - very simple.

There are two activities in Visual Studio: delayActivity and suspendActivity. I suspect that suspend is better as it probably dehydrates the workflow and saves resources.

  1. What would be the "best" way to just fire a workflow, let it sit and do nothing for several weeks and then continue (also: state machine vs. sequential)?
  2. Any help on setting it up in Visual Studio? (Needed Properties & Handlers?)

1 Answer 1


The suspendActivity stops the execution of the workflow, but doesn't permanently terminate the workflow. It is used where the workflow has an error but the error is recoverable and the workflow can be restarted at the point of failure.

The delayActivity can be used to pause a workflow for a period of time. This is the one you've got to use in your case.

The type of workflow (state machine vs sequential) depends on the requirements.

Maybe you can Google for examples, I guess there are plenty out there.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.