Table of Contents

Search

  1. Preface
  2. Workflows
  3. Workflow Variables
  4. Workflow Parameters
  5. Cluster Tasks
  6. Command Task
  7. Human Task
  8. Mapping Task
  9. Notification Task
  10. Gateways
  11. Workflow Recovery
  12. Workflow Administration

Developer Workflow Guide

Developer Workflow Guide

Human Task Restart Behavior

Human Task Restart Behavior

A Human task uses a restart recovery strategy. Unlike other task types, when an interrupted Human task restarts, it continues from the point at which it ceased operation. The Data Integration Service does not rerun the Human task from the beginning.
Consider the following rules and guidelines for Human task behavior:
  • When a Data Integration Service runs a Human task, the service creates and distributes task instances to users and groups in the Informatica domain. Each task instance identifies a subset of the workflow data that a user must analyze in the Analyst tool.
    If the Data Integration Service does not distribute all task instances before the Human task is interrupted, the service continues to distribute the task instances when it restarts the task. The Human task does not restart from the beginning.
  • If the Data Integration Service distributes all task instances before the Human task is interrupted, the Analyst tool users can work on the instances. However, if the Human task contains multiple steps, the task data cannot move from a current task instance to a task instance that another step defines. When the workflow restarts, the Human task continues from the point of interruption and the task data can move to the next step.
  • If the workflow database connection fails during task instance creation, the workflow can enter one of several different states. The workflow might fail, or the Data Integration Service might not create all of the task instances that the Human task specifies.
    If the workflow database connection fails before the Data Integration Service creates all of the Human task instances, stop the Data Integration Service. Verify that the workflow database connection is available, and restart the Data Integration Service. When the workflow recovers, the Data Integration Service tries to distribute any task instance that remains undistributed.
  • If a workflow enters an aborted state, any Human task in the workflow enters a Completed state.
If you cancel a workflow that contains a Human task and you try to redeploy the application, the Developer tool might stop responding. This might occur if you abort the workflow when the Human task is in the task creation phase. When the Human task returns control to the workflow, the Developer tool responds and deploys the application.

0 COMMENTS

We’d like to hear from you!