ARA workflow becomes Inactive status even though it has a Deployment Descriptor

Discussion created by Harriet_Kim_1764 on Dec 21, 2017
Latest reply on Dec 21, 2017 by Vlad_N
An ARA workflow contains a Deployment Descriptor.  However, it is still getting this error in the Activation report:
U00007068 Task 'RM.GENERAL.STAGE_BUILD' (Lnr: '0002') has been set to inactive because it cannot be found in the Deployment Descriptor.
Go to the workflow's History Records.
(Release Automation tab > Monitoring > highlight the workflow > in the Details pane on the right, click on 'Show History Records')


Download the Deployment Descriptor report from the workflow's History Records.


When another Component ("COM2") is added in to the Workflow ("WF") that's also mapped to the same Target, the new Component ("COM2") becomes inactive because it is using the same Package ("PK") and Profile ("PRO") upon execution.

To correct this issue, a new Package ("PK2") needs to be created whenever there is a new Component ("COM2") because the original Package ("PK") will not have any information about the new Component ("COM2") since the original Package ("PK") only has information about the original Component ("COM").