A Spin-off task is represented by a shape on the Diagram tab of a flow rule, causes a second flow to start. The second flow executes asynchronously and independently from the current flow execution. The initial flow does not pause or wait for results from the second flow. The second flow may operate on the same or a different work object from the first flow.

When two flows operate on a single work object or on related work objects, design and plan locking relationships carefully to avoid deadlocks.

Spin-off tasks support multitasking or parallel operation of work processing at the workflow level. One department or business unit can, at its own pace and following its own flows, perform its functions for the work object while another department also works on the same work object.

Increased parallelism can improve end-to-end resolution times, resulting in greater overall utilization of staff and improved customer service.

Don't confuse business process parallel processing with computational parallel processing. The original and spun-off flows execute asynchronously and independently, but within the same Java thread on the same node. Two flows that contain only utility tasks do not execute in parallel when examined at the computational level of microseconds. Q-1268

	flow, task, Split-ForEach task, Split-Join task
	Flow form — Editing in Visio — Spin-off tasks

Definitions — S