When the advanced recordset tries to process a recordset that does not exist it does not throw an error but instead makes the rest of the workflow unresponsive.
Hi! Um, can you give some simple steps I can use to reproduce this behavior? I executed a simple workflow like this on version 126.96.36.199 but it's not behaving exactly the way you described:
Note that if you have an 'On Error' variable the tool won't throw any errors.
Customer support service by UserEcho