Captive 9 – is anyone else running into Advanced Actions working in a document and then not working in another version of the same document? The elements and names have stayed the same. Is there a troubleshooting or debugging sett

I agree with Lilybiri that 99.9% of the time it is user error, can't ever actually think of a case that it wasn't, but I do have a debugging suggestion.  Add an action to you advanced action that is 'execute javascript'. 

In that script window put console.log('triggered'); Publish or preview your project in HTML5 browser.  Open the developer console in Chrome or whatever browser you prefer (this is cmd +J in chrome (mac)), just about every browser has one. 

if you see the word triggered in the console, you can at least know that you action is firing.  Certainly you can change the message to whatever you like if there is a handful of actions you are wondering about.

Hope that helps!

Brian

I have written quite a bunch of advanced actions (look at my blog) and learned that what you describe is in 99% of the cases due to the developer. Are you sure the names indicate the right object, that you don't have duplicate names (even for totally different items)? That the actions are triggered by the correct event? Do you use variables, are those variables defined and did they get the correct initial value? Was it not possible to use shared actions, especially since you talk about different projects?