Inbound Task Queue State Transitions 

As described above, unlaunched workflow jobs, steps that are part of a running job, and completed and deleted jobs all appear as tasks in a user’s inbound task queue.

Moreover, the tasks appear in a variety of states, and move from the inbound task queue of one user to that of another as the task moves from user to user and the job moves from step to step.

The tasks that appear in an inbound task queue and the state transitions that they undergo as a result of user actions are illustrated in figure below.

A single step in a workflow can spawn multiple Available or Received tasks, each of which is a user-specific instance of the step.

The owner of a workflow sees all of the tasks for a job, including a separate instance for each user to whom it is Available or by whom it has been Receivedand is not yet complete.

In the figure above, the uppper paths to Available correspond to a pull, and the lower paths directly to Received correspond to a push. Recall that whether the push occurs automatically or whether the push/pull is manual and up to the sending user depends upon the Execution Type setting of the current or receiving step. For more information, see Push versus Pull.