Failure in set Status node then in Mark Resolve Timer

[Berto2002]

Got an error on Set Status node. UI refresh worked to clear it

Then got this error in this node and cannot clear it any how. Anyone else seen this?

Xmlmc method invocation failed for BPM invocation node '08c4c556-a207-8cac-2e59-65f2cb9e154a/flowcode-b7eff10d': <methodCallResult status="fail"> <state> <code>0207</code> <service>apps</service> <operation>markRequestFixTimer</operation> <error>/apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_timers_helper.js(441): error X1001: Uncaught TypeError: Cannot read property &apos;elapsedWorkingTime&apos; of undefined</error> <flowcodeError> <where>Execute</where> <filename>/apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_timers_helper.js</filename> <lineNumber>441</lineNumber> <columnPos>25</columnPos> <message>Uncaught TypeError: Cannot read property &apos;elapsedWorkingTime&apos; of undefined</message> <errorCode>1001</errorCode> <stackTrace>markFix at /apps/com.hornbill.servicemanager/entities/Requests/fc_modules/requests_timers_helper.js(441:26)</stackTrace> <stackTrace>at /apps/com.hornbill.servicemanager/flowcode/fc_bpm/markRequestFixTimer.js(6:71)</stackTrace> </flowcodeError> </state> </methodCallResult>

[Jim]

I've ran into all sorts of random and odd errors the past few months, most of the time just restarting the processes continued them without editing anything as well, I've now got a persistent error with Parallel processes not unsuspending and I have to keep logging a request with hornbill for them to continue them. 

 

I would assume the obvious dependency is met, that the request timer was started and actually did start? 

[Berto2002]

1 minute ago, Jim said:

I've now got a persistent error with Parallel processes not unsuspending

We are also logging instances of this on a regular basis. Glad you are too; we've actually had to tell our service desk to work more slowly to avoid these! Serious issue...

@Jim am I right that the set status resolved also by default marks the resolved timer? I just wonder if I can remove the markresolvetimer node as the previous node sets resolved...

[Jim]

Just an idea to progress it, Sometimes I change the node to a 'get request details' node, purely so it will continue. This will help remove the error, you could then use an Autotask to set the timer as a one off 

[Jim]

Just now, Berto2002 said:

we've actually had to tell our service desk to work more slowly to avoid these! Serious issue...

Same here! It felt a very strange comment to have to make as well  

[Jim]

Just now, Berto2002 said:

 am I right that the set status resolved also by default marks the resolved timer? I just wonder if I can remove the markresolvetimer node as the previous node sets resolved...

This I do not know, I would imagine it does not being as there is function specific to do so? but no clue, we have the set timers in all processes that require it