SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

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

I have a MOSS2007 site that requires me to use the primary/secondary workflow approach. My workflows work perfectly on their own when I create tasks manually.

When I use the primary workflow to create tasks in the Task list the workflow associated with the Task list does not fire. In fact I cannot even start it manually as the content type created for these "special" tasks is not associated with any workflow.

Any ideas for a work around or do I need to redesign my approach?

share|improve this question

closed as too localized by Alex Angas Jun 7 '11 at 21:20

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Did you ever find the answer (or a workaround) for this that you can add below? – Alex Angas Jun 6 '11 at 6:00
I redesigned my workflow to be simpler – Mike Polen Jun 7 '11 at 14:43
OK thanks Mike. I'm going to close this question as it doesn't look like we'll ever get an answer on it. If there's any problem with that please raise it on Meta. – Alex Angas Jun 7 '11 at 21:20
Hi Mike - just in case you're still wondering what was going on with that workflow it looks like it was all "by design" that tasks created by workflow (using the system account) cannot themselves start a workflow.… – Tim Feb 23 at 16:10