Jump to content

Adam@Greggs

Hornbill Users
  • Posts

    43
  • Joined

  • Last visited

Posts posted by Adam@Greggs

  1. 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. 

     

    image.png.de46e4e0d07efc852f482cc406409ec5.png

    • Thanks 1
  2. We have a problem this morning where our support analysts are unable to log requests on behalf of shops unless they are also subscribers. As an example, shops can log requests against EPOS hardware, but we don't want to make that available to colleagues around our offices. When the support analysts log requests, they need to be able to log EPOS hardware requests on the shops behalf (if for whatever reason the shops can't access Self-Service portal). Yesterday this worked fine, but today they can't log against services unless they're also a subscriber.

  3. We're frequently seeing Hornbill SM performance slow to a crawl. This affects the admin, live and customer screens and can last for some time. We've carried out a full re-index of Hornbill ITSM and it hasn't helped. Given we're the only ones experiencing this, is there anything else we should look at our side?

  4. @James Ainsworth I've created a brand new service and applied a prog cap and BPM to it and we still receive the same error. It's almost as if when the prog capture ends, the BPM doesn't start:image.png.d5cf6803f4ed1379b8ee69862f09301e.png

    Requests until mid-morning yesterday were fine, but then we started to receive notifications that some were receiving to error message. 

    Starting to become a more major problem as the shop contact form that converts their ID into their Hornbill ID isn't working and impacting operation.

     

  5. Thanks for the advice.

    I've added defaults where there wasn't any and checked for disabled processes, but still getting the error. The HUD is also not displaying on any new requests where the error appeared (which is all at the moment), but on existing requests the HUD is displaying fine. It seems that only change requests are failing to assign, the SR and IN apply to teams fine and just receive the error and don't see the HUD in the request.

    Anything else we can check?

×
×
  • Create New...