Jo Sword Posted August 19, 2019 Share Posted August 19, 2019 Hi On a couple of our projects we are getting the following message when adding, amending or completing a task, although if we press refresh it then comes into sight or is completed. Is there anything you can do to stop this happening? FlowCode Exception (com.hornbill.projectmanager/entities/ProjectTasks/fc_ops/completeProjectTask): nodeName: Invoke Flowcode: updateProjectMilestone; nodeId: 5352eb89-e00b-4142-9a03-b9d33e4b23d9; At 540/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.projectmanager/ProjectMilestones::updateProjectMilestone] FlowCode Exception (com.hornbill.projectmanager/entities/ProjectMilestones/fc_ops/updateProjectMilestone): nodeName: Invoke Flowcode: bmUpdateCardTypeProject; nodeId: 62d411b5-e788-4bc5-839c-9081ae138e64; At 379/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.projectmanager::bmUpdateCardTypeProject] FlowCode Exception (com.hornbill.projectmanager/flowcode/fc_ops/bmUpdateCardTypeProject): nodeName: Invoke Flowcode: updateCard; nodeId: b00fbfa4-c8be-4ead-82b0-2bf1bc761395; At 153/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.boardmanager/Card::updateCard] FlowCode Exception (com.hornbill.boardmanager/entities/Card/fc_ops/updateCard): nodeName: Update Card; nodeId: b9e6bd6a-057a-47e3-8b93-074bfdb84e2a; At 174/1: "Uncaught TypeError: Cannot read property 'record' of undefined" throw(e); _fc_node_exec_b9e6bd6a_057a_47e3_8b93_074bfdb84e2a" throw(e); _fc_node_exec_b00fbfa4_c8be_4ead_82b0_2bf1bc761395" throw(e); _fc_node_exec_62d411b5_e788_4bc5_839c_9081ae138e64" throw(e); _fc_node_exec_5352eb89_e00b_4142_9a03_b9d33e4b23d9 Kind regards Jo 1 Link to comment Share on other sites More sharing options...
AlexTumber Posted August 19, 2019 Share Posted August 19, 2019 @Jo Sword can I ask, are these old projects that you are seeing problems with? Alex Link to comment Share on other sites More sharing options...
Jo Sword Posted August 19, 2019 Author Share Posted August 19, 2019 @AlexTumber yes these were from last year 1 Link to comment Share on other sites More sharing options...
AlexTumber Posted August 19, 2019 Share Posted August 19, 2019 @Jo Sword ok thanks, let me speak with our support team about this. Alex Link to comment Share on other sites More sharing options...
Victor Posted August 19, 2019 Share Posted August 19, 2019 @Jo Sword we would need a support request raised for this but unfortunately you are not a supported contact ... perhaps @Paul Alexander can give us a hand here regarding the support request? Link to comment Share on other sites More sharing options...
Jo Sword Posted August 19, 2019 Author Share Posted August 19, 2019 @Victor, thank you for your reply, @Paul Alexander is current;y on annual leave, I will ask @Darren Rose is he can raise for me. Kind regards Jo 1 Link to comment Share on other sites More sharing options...
Darren Rose Posted August 19, 2019 Share Posted August 19, 2019 @Jo Sword @Victor @AlexTumber I'll get the support request raised 1 Link to comment Share on other sites More sharing options...
Deen Posted August 29, 2019 Share Posted August 29, 2019 This particular issue turned out to be a Project Manager defect that was corrected in the following 272 release: Taking this update will prevent the problem from occurring again. 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