Jump to content

Recommended Posts

Posted

We have a workflow with a Suspend set up as below.

image.png.89dcee27317255bc1d473950682a9e6d.png

The goal is to have this ticket assign for an initial team for triage. Once that team assigns it the following Human Tasks assign to the new owner and an email goes out to the customer with the new owner's name. In practice this node is freezing all of the tickets at this node. No assignments or any action I have tried is able to pass this suspend. Am I misunderstanding/ misconfiguring this node? 

 

Posted

There is actually a wait for request owner and wait for new request owner nodes which may be more applicable, I think there is also wait for team potentially not too sure on that latter one though

  • Like 1
Posted

Wait for Request Update does exactly what it says - it waits for an Update, nothing else.
In this context Update is a Timeline Action of type "Update"

As Jim mentions, waiting for an Assignment is via the Wait for [New] Request Owner node.

  • Like 1

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...