Berto2002 Posted April 6 Share Posted April 6 I have a node configured like this: And which fell into error: 12.231338s ERROR Execution Failed: Xmlmc method invocation failed for BPM invocation node 's1/flowcode-6ebcf2ee': <methodCallResult status="fail"> <state> <code>0200</code> <service>apps</service> <operation>updateReqHoldStatus</operation> <error>FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/updateReqHoldStatus): nodeName: Invoke Flowcode: Update Request Sub-status; nodeId: 43f485c9-6101-49cb-9f5f-28f843ced23d; At 386/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.servicemanager/Requests::systemSmUpdateSubstatus] /apps/com.hornbill.core/flowcode/fc_modules/xmlmc.js(189): error X1001: Uncaught EspMethodCall::invoke: Operation[data::entityUpdateRecord] Superfluous entity record update detected for 'Requests'. The primary record was updated but no data changes were applied." throw(e); _fc_node_exec_43f485c9_6101_49cb_9f5f_28f843ced23d</error> </state> <flowCodeDebugState> <step>43f485c9-6101-49cb-9f5f-28f843ced23d</step> <executionId>a530f241-279c-45f1-890c-05f213c5676d</executionId> </flowCodeDebugState> </methodCallResult> I don't know what was wrong but I just re-loaded the record from the UI and it ran-through fine. It's a bit odd because at 10.09 there is a second entry in the timeline that it's been taken off hold again; this node must have done that... Was this a back-end blip or is there something in my configuration that is not right that strangely made it fail to put on hold and therefore set to in progress again on first run but succeed on restart? Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now