Unable to"assignteamowner"

[Kelvin]

Since the resent patches, All of our change requests (75) show the following error

How do we resolve this. 

The problem is they are part way through our change process and need to be progressed

[Steve G]

Hi @Kelvin,

Were the Change Requests that are affected by this issue raised prior to you upgrading to Service Manager v2.36.5? And are new Change Requests also affected by this issue? The reason I ask is that we fixed this issue in v2.36.4, which was released on Wednesday morning (this week).

If this is just affecting Change Requests raised prior to the 2.36.4 release, then the workflows will need to be restarted on the affected requests to retry the failed node.

Kind regards,

Steve

[Martyn Houghton]

@Kelvin

The posts below may also give you some background info as well to why it happened.

Cheers

Martyn

 

[Kelvin]

@steve_g This is only happening to those raised before the patch was released. How do I restart the workflows.

[Steve G]

Hi @Kelvin,

There is a button to the right of the BPM display on the affected requests (see attached image). Clicking this will attempt a re-run of the failed workflow node.

You need to have the Service Desk Admin role against your user account to be able to access this button.

Kind regards,

Steve

 

[Kelvin]

Perfect, Thanks