Jump to content

Suspend node appears to be ignored in BPM


Recommended Posts

Hi

I have a script with a suspend node setup (screenshot below) which appears to be ignoring the suspend node. This was working yesterday with no issues, but after an update last night to the latest build of Service Manager on our MEHT instance, the script appears to be skipping this suspend node and is just going straight onto the Complete stage as it is seeing the request in a Resolved state straight away, and moving it to closed (previously it was suspending the call for a set period before moving onto the decision node). NB I have this set to an hour suspend for testing purposes. Also the instance of Hornbill had not had an update since December and it was updated to the latest build last night.

Can anyone advise further at all please?

779657968_StatusChangeNode.thumb.PNG.0a3a36ae6a53512589e89ff3b62ac319.PNG

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...