Adam@Greggs

Will this fix any existing or will we need to go into each one and rerun the node that it's stuck on?

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.

Whenever I make a change to the default IC or BPM, the changes are ignored anyway and it stays with the default one that (strangely) collects the asset details. I think there could be a bug with it perhaps.

@ArmandoDM Working for us now as well

@ArmandoDM If an analyst logs a ticket on behalf of someone who subscribes to the service, but doesn't have the service themselves then it won't appear.

Sorry, I've just posted this as well. We're affected by this. If you add your support analyst as a subscriber, they'll be able to support it, but also see it as a subscribed service (which you don't want)

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.

Looks to be fine again now - thanks!

Same for us

We're affected by this as well

+1 Getting intermittent drops as well

We're fine now as well

Us as well....

Just to +1 this - We're having the same issue and it's preventing users raising change requests in our Change management service.

@Ehsan Thanks - it's worth noting that the emails are actually sending, it seems like we get the error, the call doesn't update to say the email is sent, but the recipient actually receives the email fine.