question

You can Release it before it's finished returning to a park position and them pre-empt that return job by issuing a pre-empting task sequence with a higher priority - if that's what you want to do.

Most people's use of the Resource construct is to simplify/combine together the concepts of zones/ lists, references and task executers for a seemingly more complete solution, but the truth is that these concepts are still operating in the background ready for you to customize and override behaviors. You may choose just to implement those behaviors yourself and avoid the use of Resources entirely.

A Resource that refers to a group of objects actually just a list that exists in the background. Both value and puller are list concepts and might be easier to understand if you think about the Resource as a list as well.

1. The value is the thing on the list the query currently evaluates. For example "WHERE value.Type == 3" would filter for objects with a Type label of 3. In both the Acquire and Pull from List activities, if you type a string that is not some keyword into the query, will interpret it as a label on the value. So normally you'd only type "WHERE Type == 3". So you only really ever use value in cases where the actual object reference needs to be passed into a function.

2. Similarly, puller refers to the 'thing' that is trying to pull something from the list. In the Pull from List activity the user can specify the puller (the token by default). In an Acquire activity the puller is always the token.