Adam@Greggs Posted January 16 Share Posted January 16 We're seeing our self-service tickets produce an xml error this morning. If you go into the failed instance in "Manage Executed Workflows" and re-run the failed part, it then continues but hits another error, which you can also re-run and allow the request to process as normal. The two Hornbill automations are just auto assigning to a group and automatically setting a medium priority. 1 Link to comment Share on other sites More sharing options...
Alistair Young Posted January 16 Share Posted January 16 Hi all, we've got similar trouble this morning - we've seeing this irrespective of how the ticket has been raised. 1 Link to comment Share on other sites More sharing options...
AlexTumber Posted January 16 Share Posted January 16 @Adam@Greggs @Alistair Young thanks for your posts. We are currently investigating. Hoping to have a resolution shortly. Alex 3 1 Link to comment Share on other sites More sharing options...
Deen Posted January 16 Share Posted January 16 @Adam@Greggs @Alistair Young Our developers have found the root cause of the problem and are working on a fix. I'll let you know when a patch is deployed. 3 Link to comment Share on other sites More sharing options...
Sana Posted January 16 Share Posted January 16 Any update on this? Link to comment Share on other sites More sharing options...
Nanette Posted January 16 Share Posted January 16 @Sana@Adam@Greggs@Alistair Young We have deployed a fix to resolve this issue. Apologies, for any inconvenience this may have caused. Link to comment Share on other sites More sharing options...
Alistair Young Posted January 16 Share Posted January 16 1 minute ago, Nanette said: @Sana@Adam@Greggs@Alistair Young We have deployed a fix to resolve this issue. Apologies, for any inconvenience this may have caused. Thanks Nan Alistair 1 Link to comment Share on other sites More sharing options...
Adam@Greggs Posted January 16 Author Share Posted January 16 6 minutes ago, Nanette said: @Sana@Adam@Greggs@Alistair Young We have deployed a fix to resolve this issue. Apologies, for any inconvenience this may have caused. Will this fix any existing or will we need to go into each one and rerun the node that it's stuck on? 1 Link to comment Share on other sites More sharing options...
Steve Giller Posted January 16 Share Posted January 16 5 minutes ago, Adam@Greggs said: Will this fix any existing or will we need to go into each one and rerun the node that it's stuck on? Regrettably, any Workflows in a Failed state will need manually restarting. We apologise for any inconvenience that this will cause. 1 1 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