chriscorcoran Posted January 14, 2020 Share Posted January 14, 2020 I'm getting an error when putting calls on hold since the latest service manager update. FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/smUpdateStatus): nodeName: API Call - systemSmUpdateStatus; nodeId: 15ccd0bd-6cc4-4151-94f1-95008f16b270; At 109/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.servicemanager/Requests::systemSmUpdateStatus] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/systemSmUpdateStatus): nodeName: API Call: Clear Request Sub-status; nodeId: 151caee3-58c2-4106-a5eb-769c7cf35cfb; At 808/1: "Uncaught EspMethodCall::invoke: Operation[data::updateRecord] There are no values to update" throw(e); _fc_node_exec_151caee3_58c2_4106_a5eb_769c7cf35cfb" throw(e); _fc_node_exec_15ccd0bd_6cc4_4151_94f1_95008f16b270 Any ideas? Link to comment Share on other sites More sharing options...
chriscorcoran Posted January 14, 2020 Author Share Posted January 14, 2020 ignore I have seen its been logged already on the forums. Link to comment Share on other sites More sharing options...
Steve Giller Posted January 14, 2020 Share Posted January 14, 2020 @chriscorcoran As noted in the other thread, your Instance has also been patched. Link to comment Share on other sites More sharing options...
Michael Sharp Posted January 14, 2020 Share Posted January 14, 2020 9 hours ago, Steve Giller said: @chriscorcoran As noted in the other thread, your Instance has also been patched. We're still plagued by this!! Mike. Link to comment Share on other sites More sharing options...
Julie McClelland Posted January 15, 2020 Share Posted January 15, 2020 Hello, We are still getting this message when placing calls on hold. thanks Julie. Link to comment Share on other sites More sharing options...
Recommended Posts