'Create Catalog Task' Action with the Wait box selected does not create the task, it just waits. What's the deal?

JR42
Giga Guru

If I check the box called, Wait, within the 'Create Catalog Task' Action, then test the flow, the flow does not create the catalog task.  The flow stops on the 'Create Catalog Task' Action with a status of waiting.

I expected it to create the catalog task, then wait for that catalog task be be closed.  Is that not the expected behavior?

What is it waiting for, if not that?

 

find_real_file.png

find_real_file.png

 

 

1 ACCEPTED SOLUTION

Sai Kumar B
Mega Sage
Mega Sage

@Justin 

The wait checkbox is to wait till the catalog task is closed

Reference - https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/flow-designer/refere...

Wait

Pauses the flow until this task completes and is no longer active (active=false).

Alternatively, you can add a wait condition by dragging-and-dropping a true/false field from the data panel into the Wait field. The flow only waits for the task to complete when this field is true.

View solution in original post

5 REPLIES 5

Sai Kumar B
Mega Sage
Mega Sage

@Justin 

The wait checkbox is to wait till the catalog task is closed

Reference - https://docs.servicenow.com/bundle/sandiego-servicenow-platform/page/administer/flow-designer/refere...

Wait

Pauses the flow until this task completes and is no longer active (active=false).

Alternatively, you can add a wait condition by dragging-and-dropping a true/false field from the data panel into the Wait field. The flow only waits for the task to complete when this field is true.

The 'Create Catalog Task' action is not creating the Task, it is just waiting.

 

 

 

@JR42,

Why do you say there was no task created?  What does Execution history show?  Did you look at the Task table?

Hi ricker, this was awhile back, but I believe the issue was domain related. The tasks were created, but not in the correct domain, so they did not appear on the task related list on the RITM.  I probably ended up applying the domain with the create action.