Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.2.1
  • All Products

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

Back Next

Workflow Recovery Examples

Workflow Recovery Examples

The following examples describe interrupted workflow instances and describe how the Data Integration Service tries to recover each instance. In each example, the workflow is enabled for recovery and each task is a Command task, a Mapping task, or a Notification task.
The workflow encounters the following interruptions:
You cancel the workflow instance.
You cancel the workflow instance while Task 2 is running. The Data Integration Service completes Task 2 and then cancels the workflow instance. The three tasks and the workflow instance have the following states:
Task 1 (Completed) > Task 2 (Completed) > Task 3 (Not Started). Workflow is Canceled.
When the workflow recovers, the Data Integration Service passes over Task 1 and Task 2 and runs Task 3 for the first time.
You abort the workflow instance while a task with a skip recovery strategy is running.
You abort the workflow instance while Task 2 is running. Task 2 has a skip recovery strategy. The Data Integration Service aborts Task 2 and then aborts the workflow instance. The three tasks and the workflow instance have the following states:
Task 1 (Completed) > Task 2 (Aborted) > Task 3 (Not Started). Workflow is Aborted.
You cannot recover the workflow instance because you aborted the workflow.
The Data Integration Service process shuts down unexpectedly. The workflow is configured for recovery.
The Data Integration Service process shuts down while Task 2 is running. Task 2 is a Notification task. The three tasks and the workflow instance have the following states when the service process restarts:
Task 1 (Completed) > Task 2 (Canceled) > Task 3 (Not Started). Workflow is Canceled.
When the workflow recovers, the Data Integration Service passes over Task 1, restarts Task 2, and runs Task 3 for the first time.
A task with a restart recovery strategy encounters a recoverable error.
Task 2 has a restart recovery strategy and encounters a recoverable error. The service cancels Task 2 and then cancels the workflow instance. The three tasks and the workflow instance have the following states:
Task 1 (Completed) > Task 2 (Canceled) > Task 3 (Not Started). Workflow is Canceled.
When the workflow recovers, the Data Integration Service passes over Task 1, restarts Task 2, and runs Task 3 for the first time.
A task with a skip recovery strategy encounters an error. You cancel the workflow instance.
Task 2 has a skip recovery strategy. The task encounters an error and fails. The outgoing sequence flow does not contain a condition to verify that Task 2 succeeded. As a result, the Data Integration Service continues to run subsequent workflow objects. You cancel the workflow instance while Task 3 is running. Task 3 has a restart recovery strategy. The Data Integration Service cancels Task 3 and then cancels the workflow instance. The four tasks and the workflow instance have the following states:
Task 1 (Completed) >Task 2 (Failed) > Task 3 (Canceled) > Task 4 (Not Started). Workflow is Canceled.
When the workflow recovers, the Data Integration Service passes over Task 1 and Task 2, restarts Task 3, and runs Task 4 for the first time. During the recovery run, Task 3 and Task 4 complete successfully. The Data Integration Service updates the final workflow state to Completed.
A task with a skip recovery strategy encounters an error. You abort the workflow instance.
Task 2 has a skip recovery strategy. The task encounters an error and fails. The outgoing sequence flow does not contain a condition to verify that Task 2 succeeded. As a result, the Data Integration Service continues to run subsequent workflow objects. You abort the workflow instance while Task 3 is running. Task 3 has a restart recovery strategy. The Data Integration Service aborts Task 3 and then aborts the workflow instance. The four tasks and the workflow instance have the following states:
Task 1 (Completed) >Task 2 (Failed) > Task 3 (Aborted) > Task 4 (Not Started). Workflow is Aborted.
You cannot recover the workflow instance because you aborted the workflow.
A task with a skip recovery strategy encounters an error. The outgoing conditional sequence flow checks for task failure.
Task 1 has a skip recovery strategy. The task encounters an error and fails. The outgoing sequence flow contains a condition to verify that Task 1 succeeded. Because the condition returns false, the Data Integration Service stops processing subsequent workflow objects and completes the workflow instance. The three tasks and the workflow instance have the following states:
Task 1 (Failed) > Task2 (Not Started) > Task 3 (Not Started). Workflow is Completed.
You cannot recover the workflow instance because the workflow instance completed.
A task fails due to a task error in a workflow that does not support recovery.
Because the workflow does not specify a workflow recovery strategy, the Data Integration Service skips any task that fails due to a task error. The workflow can run to completion. The three tasks and the workflow instance have the following states:
Task 1 (Completed) > Task2 (Failed) > Task 3 (Completed). Workflow is Completed.
You cannot recover the workflow instance because the workflow instance completed.
A mapping in a Mapping task generates no exception data for a Human task. The active sequence flow in the workflow reaches a Terminate event.
Task 1 is a Mapping task and Task 2 is a Notification task. The Mapping task generates exception data for a downstream Human task. The Notification task sends an email that contains the number of exception rows that the mapping in the Mapping task generates. The workflow includes an Exclusive gateway that connects to the Human task and to a Terminate event.
The first sequence flow on the gateway connects to the Terminate event and includes a condition that evaluates the output from the Mapping task. The second sequence flow on the gateway connects to the Human task. Because the mapping that Task 1 specifies generates no exception data, the conditional sequence flow on the gateway triggers the Terminate event. The tasks and the workflow instance have the following states:
Task 1 (Completed) > Task 2 (Completed) > Terminate event. Workflow is Aborted.
You cannot recover the workflow because the workflow entered an aborted state by design.
0 COMMENTS
We’d like to hear from you!