Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(1 Rating)
facebook Twitter
Print Bookmark Alert me when this article is updated


FAQ: When is the status of the "Merge Task" set to "Closed" in MDM?

In Master Data Management (MDM), a merge task is created by:

  • Manually from Informatica Data Director (IDD) by finding for merge candidates and create a task to merge them.
  • The task assignment daemon when two records are queued for a Manual Merge from a batch and are unassigned yet (or a code that makes use of the task assignment procedure to assign tasks).  

The status of the merge task is set to CLOSED in the following two instances:

  1. When the task is cancelled by the user.
  2. When a merge is performed from the IDD application from the task context (the Subject Area record is opened by opening the task and not by directly opening the Subject Area record).

More Information

Some common operations that set the task status to OBSOLETE are as follows:

  1. When a merge is performed in the Potential Matches tab of the Subject Area record by opening the record directly from a search or as a link (and not as part of the task). This also includes a merge that is performed either from the Merge Manager or a Services Integration Framework (SIF) MultiMerge API.
  2. When the record is set as a Not A Match from the IDD application from the task context.
  3. When the record is set to Queue For Merge from the IDD application from the task context.
  4. When one of the records that is part of the merge is merged into a different record as part of a different task and hence the record no longer exists.
  5. When a non owner of the task opens the task and completes the merge operation.

Applies To
Product: MDM Multidomain
Problem Type: Configuration; Product Feature
User Type: Architect
Project Phase: Configure; Implement; Onboard
Product Version: MDM
Operating System:
Other Software:



Last Modified Date:6/2/2020 8:51 PMID:146452
People who viewed this also viewed


Did this KB document help you?

What can we do to improve this information (2000 or fewer characters)