SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Since you can't loop back in a workflow, I'd like my workflow to branch to another workflow if it reaches a point where it would need to go back. Is there an option to have my workflow start another workflow?

Thank you!

share|improve this question

migrated from Oct 21 '11 at 16:30

This question came from our site for professional and enthusiast programmers.

Did you check this page?… – Shoban Oct 21 '11 at 17:03
I was able to resolve my situation following this post… – Daniela Aug 27 '14 at 16:58

Check out Useful Sharepoint Designer Custom Workflow Activities and particularly Start Another Workflow.

share|improve this answer
I second this approach. We have used this activity in several production workflows. I would point out, though, you may need to consider a 1 minute wait on the child workflow so that the parent has time to fully exit. – Robert Kaucher Mar 21 '12 at 17:35

Having a pair of workflows triggering each other is a common way to build loops in SharePoint Designer.

Since your workflow starts when an item is changed, you just need to have the first workflow modify a field. This will trigger the second workflow.

share|improve this answer

Even am facing the same issue. On item update, SP 2010 designer workflow will not re-initiate or there is no default action to start another workflow or the same (which was avail in SP 2007 designer WF).

Can go for custom workflow activities else can use event handlers hopefully.

Looping back, infinite looping are all possible if you will check on some particular field's value from the workflow.

Can get a clear view in this link:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.