000038640 - RSA Archer Advanced Worflow(AWF) jobs fail on an update content node and never process

Document created by RSA Customer Support Employee on Mar 26, 2020
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000038640
Applies ToRSA Product Set: RSA Archer
RSA Version/Condition: 6.X
 
IssueWhen some jobs process through an update content node it fails. Even if the rules on the node in the latest workflow process version look good and updating the job to the latest workflow process version does not fix the issue.

<E2ETraceEvent xmlns="http://schemas.microsoft.com/2004/06/E2ETraceEvent">
    <System xmlns="http://schemas.microsoft.com/2004/06/windows/eventlog/system">
        <EventID>0</EventID>
        <Type>3</Type>
        <SubType Name="Error">0</SubType>
        <Level>2</Level>
        <TimeCreated SystemTime="2020-02-25T19:38:11.6108209Z" />
        <Source Name="Archer.NET" />
        <Correlation ActivityID="{00000000-0000-0000-0000-000000000000}" />
        <Execution ProcessName="WpServiceHost" ProcessID="10432" ThreadID="5252" />
        <AssemblyVersion>6.5.500.1003</AssemblyVersion>
        <Computer>SERVERNAME</Computer>
    </System>
    <ApplicationData>
        <TraceData>
            <DataItem>
                <TraceRecord Severity="Error" xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord">
                    <TraceIdentifier>Archer.NET</TraceIdentifier>
                    <Description>Unhandled exception occurred: [Script: UpdateContentScript] [NodeId: 155841:CUST] [JobId: 6652:CUST] [ProcRef: 60ebee56a785fa8f]</Description>
                    <AppDomain>WpAppDomain~1</AppDomain>
                    <Exception>
                        <Message>
---------- Exception ----------
[System.InvalidOperationException]
Failed to Update Content for record 275058
   at ArcherTech.Services.WorkflowService.Scripts.Scripts.CompleteNodeWithErrorCommand`1.Execute(T context)
   at ArcherTech.Utility.ExecutionTask.PlanExecutionCommand`1.Execute(T context)
   at ArcherTech.Services.WorkflowService.Scripts.ScriptController.Run[T](IWorkpointScript workpointScript)
---------- Inner Exception 1 ----------
[System.NullReferenceException]
Object reference not set to an instance of an object.
   at ArcherTech.Services.WorkflowService.Scripts.Scripts.UpdateContentScript.ValuesListFieldStrategy.ConstructContentField(UpdateContentScriptContext context, FieldSetting fieldSetting)
   at ArcherTech.Services.WorkflowService.Scripts.Scripts.UpdateContentScript.ConstructUpdateContentCommand.Execute(UpdateContentScriptContext context)
   at ArcherTech.Utility.ExecutionTask.CompositeCommand`1.Execute(T context)
   at ArcherTech.Utility.ExecutionTask.CompositeCommand`1.Execute(T context)
   at ArcherTech.Utility.ExecutionTask.PlanExecutionCommand`1.Execute(T context)</Message>
                    </Exception>
                </TraceRecord>
            </DataItem>
        </TraceData>
    </ApplicationData>
</E2ETraceEvent>


 
CauseThe AWF job references guid's for the field and values list items. If there is a change to the fields such as a guid change or values list items are removed but nodes in old process versions of Advanced Workflow still reference the old guid's, the node will fail. The job retains the old guid's associated with the node even if updating the job to the latest workflow process version.
ResolutionThe first thing you must do is ensure that all the updates that are performed by the node are valid in the application builder for the module. Once this is done, you have a few options to correct the issue:
  1. Cancel the Workflow job, and re-enroll it.
  2. Re-create the node in the application builder then update the job to the latest version.
  3. Manually update the guids for the node in the workflow job that is failing.
    1. Open up the job in the job troubleshooter.
    2. Select the failed content update node.
    3. Scroll down on the right until you get to the User Data section.
    4. Under the Bulk User Data click the pencil icon to the right of each of the field types getting set.
User-added image

 
                       After clicking the pencil icon, you can what the guids are.
 
User-added image

                       5. You can compare this to a record that is on the latest workflow process version and copy the values from the new job to the bad job so that it matches.
                       6. Once this is done you can save the bad job.
                       7. From the Job Troubleshooter on the bad job, click the node that is failing then click the reset button.
User-added image

Attachments

    Outcomes