I’ve requested this before, but thought I’d bring it up again. The workaround I have atm is to open a random action, enter a random field, press F2, select the variable name from the list and insert it - you can see its current value in the evaluation. If it turns out to be hard to make them really watchable, perhaps just showing their current value in the Action List Parameters window would help.
Steve
Hi Steve
Watching actionlist parameters is a bit tricky, we don’t currently have a way of specifying which actionlist, which instance of an actionlist etc, and action list instances have no name by which they can be referenced. It’s going to take some serious work, it’s on the todo list but not very high in priority at this stage (as you know, we have lots of other work going on at the moment!).
As a quick solution, could you make the Watches tab context-dependent. So, say you had an action list parameter called “foo” in some action list F, and you set up a watch on “foo”. If you’re on the F tab, it would show the value. If you’re on a different tab, it might show “no variable called foo”. Etc.
Or show them as subnodes of the Action Lists in the Project tab, with their current values (if any). (hmm, though I see what you mean about current instance…)
Or allow watch/evaluate of arbitrary strings. Then the value of %foo% just depends on where the run is currently up to.
Or allow macros to reference action list parameters - just tried this workaround and it didn’t seem to work.
Or show Run Action List calls in the Build Log even when Show Full Log is off.
Or something. Hmm. 
Steve