Keith Posted March 12, 2018 Share Posted March 12, 2018 Our system was updated to build 2892 in the early hours of this morning and as a result requests are no longer being assigned to teams nor are we able to assign. We are receiving flowcode errors on every request. I have raised an emergency request but as yet have not had any response. Can someone please investigate and get back to myself or Marc Crabb urgently. Regards Keith Link to comment Share on other sites More sharing options...
Guest Chaz Posted March 12, 2018 Share Posted March 12, 2018 @Keith we're investigating the cause and will post back when we have more info Link to comment Share on other sites More sharing options...
HGrigsby Posted March 12, 2018 Share Posted March 12, 2018 Us too. Please can someone contact as soon as possible. Unable to log any calls Link to comment Share on other sites More sharing options...
Keith Posted March 12, 2018 Author Share Posted March 12, 2018 OK thanks @Chaz Link to comment Share on other sites More sharing options...
m.vandun Posted March 12, 2018 Share Posted March 12, 2018 We are getting the same issue. Link to comment Share on other sites More sharing options...
Martyn Houghton Posted March 12, 2018 Share Posted March 12, 2018 We are also getting the same assign issues. Link to comment Share on other sites More sharing options...
chriscorcoran Posted March 12, 2018 Share Posted March 12, 2018 Same issues here Link to comment Share on other sites More sharing options...
chriscorcoran Posted March 12, 2018 Share Posted March 12, 2018 37161 2018-03-12 08:11:29 error comms 9096 FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_bpm/assignTeam): nodeName: Invoke Flowcode: Assign; nodeId: c0a752d7-936d-439c-8d54-de2011101914; At 352/1: "Uncaught EspMethodCall:invoke: Operation[apps/com.hornbill.servicemanager/Requests:assign] FlowCode Exception (com.hornbill.servicemanager/entities/Requests/fc_ops/assign): nodeName: Already Assigned to Team?; nodeId: a41c9ed6-2eae-4d0b-ae02-efac08d92e78; At 476/1: "Uncaught TypeError: Cannot read property 'h_fk_team_id' of undefined" throw(e); _fc_node_exec_a41c9ed6_2eae_4d0b_ae02_efac08d92e78" throw(e); _fc_node_exec_c0a752d7_936d_439c_8d54_de2011101914 Link to comment Share on other sites More sharing options...
Guest Paul Alexander Posted March 12, 2018 Share Posted March 12, 2018 We have the same issue..... Link to comment Share on other sites More sharing options...
Gerry Posted March 12, 2018 Share Posted March 12, 2018 We are currently investigating to determine the fastest route to a fix, I will update within the next 15 minutes. Gerry 1 Link to comment Share on other sites More sharing options...
Guest Paul Alexander Posted March 12, 2018 Share Posted March 12, 2018 Quick question......how can I switch off our Service Portal so that we're not inundated with user tickets which will crash please? Link to comment Share on other sites More sharing options...
Lyonel Posted March 12, 2018 Share Posted March 12, 2018 Same issues here Link to comment Share on other sites More sharing options...
Gerry Posted March 12, 2018 Share Posted March 12, 2018 Paul, I am not sure there is any easy way to do that, I am going to ask someone thats not working on the actual problem. We are still trying to identify the fastest route to resolution, I will continue to post with further updates here. Gerry Link to comment Share on other sites More sharing options...
Gerry Posted March 12, 2018 Share Posted March 12, 2018 We have identified the problem which is currently being verified and we will be applying this as a hot-fix to effected instances in the next 15 minutes or so, we are working as fast as we possibly can in order to resolve this issue. I will update again within the next 15 minutes. Gerry 2 Link to comment Share on other sites More sharing options...
Dan Munns Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
Paul Morrow Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
Gerry Posted March 12, 2018 Share Posted March 12, 2018 We have identified the problem, a fix is currently being verified so we can get it applied to the affected instances. It relates to the way certain requests are logged when data targeted to a specific column is not present, I am picking this up from the internal conversations, I will be able to provide more details soon. Gerry 1 Link to comment Share on other sites More sharing options...
Chris Temple Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
Damien P Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
BenKeeley Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
chrisnutt Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
Stuart Torres-Catmur Posted March 12, 2018 Share Posted March 12, 2018 We are getting this problem as well Link to comment Share on other sites More sharing options...
Daniel Nespoli Posted March 12, 2018 Share Posted March 12, 2018 +1 Link to comment Share on other sites More sharing options...
samwoo Posted March 12, 2018 Share Posted March 12, 2018 Us too! Link to comment Share on other sites More sharing options...
Gerry Posted March 12, 2018 Share Posted March 12, 2018 We have verified the fix resolves the issue being reported, we are just in the process of determining the fastest way to apply this, we are minutes away, thank you for your continued patience. Gerry 2 2 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now