Neil Smith Posted January 14, 2020 Posted January 14, 2020 When users try and put Incidents on-hold, they are receiving the attached error. This is purely only on Incidents, and not Service Requests. No changes have been made to the Incident process since early December, and this issue has just been occurring today. Health Check returns no issues. Can you advise what needs to be done to investigate this further and resolve the issue? Many thanks, Neil
Neil Smith Posted January 14, 2020 Author Posted January 14, 2020 @Hornbill Support Team see above, thanks
Vikki Cameron Posted January 14, 2020 Posted January 14, 2020 This is also affecting us. When we get the error it does put the call on hold, but doesn't update the timeline saying this.
Blowerl Posted January 14, 2020 Posted January 14, 2020 This is also affecting us, If you put any call on hold, we get the same message.
Philip Walker Posted January 14, 2020 Posted January 14, 2020 We have the same issue The call does actually get put on hold, but the "Reason" text doesn't get added to the call, and we get the following error message pop up and the bottom:
Steve Giller Posted January 14, 2020 Posted January 14, 2020 We are aware of this issue and are working on a resolution. As we get further information we will update this thread.
Guest Ehsan Posted January 14, 2020 Posted January 14, 2020 @Neil Smith, @Charlie Jones, @Vikki Cameron, @Blowerl, @Philip Walker, We have identified the cause of this issue. This will be patched directly to your instance very shortly. Apologies for the inconvenience that this has caused. For the Requests that were effected by this failure, a restart may automatically resume the Request's progress. Please refer to "How to restart a failed workflow" section in the Wiki document below for instructions: https://wiki.hornbill.com/index.php/Business_Process_Designer Thanks, Ehsan
Neil Smith Posted January 14, 2020 Author Posted January 14, 2020 Appreciate the quick turnaround @Ehsan, thanks again.
HGrigsby Posted January 14, 2020 Posted January 14, 2020 +1 - we also are affected by this thanks Helen
Guest Ehsan Posted January 14, 2020 Posted January 14, 2020 Hi @HGrigsby, This should be addressed on your instance now. Ehsan
Blowerl Posted January 14, 2020 Posted January 14, 2020 This is now all working. Thank you, for fixing the issue.
Michael Sharp Posted January 14, 2020 Posted January 14, 2020 4 hours ago, Ehsan said: Hi @HGrigsby, This should be addressed on your instance now. Ehsan We're still plagued by this!!! Mike.
Julie McClelland Posted January 15, 2020 Posted January 15, 2020 Hello - we are still experiencing this issue
Guest Ehsan Posted January 15, 2020 Posted January 15, 2020 @Michael Sharp, @Julie McClelland, @Paul Welby, @nasimg, @AndyHill, Your instances have been patched now. Please do remember... For the Requests that were effected by this failure, a restart may automatically resume the Request's progress. Please refer to "How to restart a failed workflow" section in the Wiki document below for instructions: https://wiki.hornbill.com/index.php/Business_Process_Designer Ehsan
nasimg Posted January 15, 2020 Posted January 15, 2020 @Ehsan Thanks this has fixed the issue for us. Nasim
Guest Paul Alexander Posted January 15, 2020 Posted January 15, 2020 We're having this issue too.....do we need to be patched? (Pressing the 'restart button gets through the stalled processes) thanks
Guest Ehsan Posted January 15, 2020 Posted January 15, 2020 @Paul Alexander, Your instance has now been patched.
Shamaila.Yousaf Posted January 16, 2020 Posted January 16, 2020 @Ehsanwe are having this issue our end also. Thanks in advance. Sxx
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