Adrian Simpkins Posted May 8, 2019 Share Posted May 8, 2019 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? Link to comment Share on other sites More sharing options...
Victor Posted May 8, 2019 Share Posted May 8, 2019 @Adrian Simpkins try and set the "From Status" from "Auto" to "Resolved" and see if it works then... Link to comment Share on other sites More sharing options...
Adrian Simpkins Posted May 8, 2019 Author Share Posted May 8, 2019 Hi Victor Thanks that is now suspending as expected - not sure if I clicked on the Focus tab as I have it set on other scripts with this flow but I may well have done Many thanks 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