Jump to content

Recommended Posts

  • 2 weeks later...
Posted

I used to get this when certain BPM workflows weren't completed properly, It couldn't find the next node after a decision. Is it only happening against certain tickets that all follow the same BPM process?

Posted

Followed the advise from this forum: 

and the decision node has been amended within Fulfillment and Closure as there was a typo within the Custom Expression for Status Closed

 

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
×
×
  • Create New...