Occasional error updating request status

[Gareth Cantrell]

Does anyone have any idea what would cause an occasional error when updating a request status?

This tends to happen when we update the request status to "Open", immediately after the "Wait for Request Owner" suspend node unsuspends.

Invariably, this happens between 22:00 and 02:00, which is when our US teams are operational, and means they cannot progress until the following day after I've had to restart all the broken worfklows.

I would very much like to understand what is causing these failures and how to mitigate them.

 

Execution Failed: Xmlmc method invocation failed for BPM invocation node 'stage-effafaaf/flowcode-8fb4d840': <methodCallResult status="fail"> <state> <code>0207</code> <service>apps</service> <operation>updateReqStatus</operation> <error>/apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_bpm_helper.js(5910): error X1001: Uncaught EspMethodCall::invoke: Operation[data::entityUpdateRecord] Superfluous entity record update detected for &apos;Requests&apos;. The primary record was updated but no data changes were applied.</error> <flowcodeError> <where>Execute</where> <filename>/apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_bpm_helper.js</filename> <lineNumber>5910</lineNumber> <columnPos>32</columnPos> <message>Uncaught EspMethodCall::invoke: Operation[data::entityUpdateRecord] Superfluous entity record update detected for &apos;Requests&apos;. The primary record was updated but no data changes were applied.</message> <errorCode>1001</errorCode> <stackTrace>updateRequestStatus at /apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_bpm_helper.js(5910:33)</stackTrace> <stackTrace>at /apps/com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqStatus.js(15:41)</stackTrace> </flowcodeError> </state> </methodCallResult>

[Berto2002]

20 minutes ago, Gareth Cantrell said:

Superfluous entity record

This is something known at Hornbill and we have an open support request for it. We have not been hit by this error ourselves lately but it's not fixed.

I think this relates to the Defect logged on portal so should ensure you have clicked I'm affected or log your own support request:

• 

[Gareth Cantrell]

@Berto2002 thanks for pointing that out - I've indicated that we're also affected by this.