This code:
if (initialization.indexOf("NKN") >= 1)
scheduleAfter (100, CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME").scheduleActions()); // set state vars

Throws this error:

ProntoScript error: Argument is not a function
Offending activity script: Tag: 'HOME'
Offending line #23: "scheduleAfter (100, CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME").scheduleActions()); // set state vars"

The .scheduleActions() is a function, is it not?
What's throwing the error?

THank you,

I think that scheduleAfter expects a function. So try:
function saveStuff(){
CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME").scheduleActions();
}
scheduleAfter (100,saveStuff);

Others on here will be able to confirm this for sure.

That is correct. The error message indicates what is the problem. In fact, the Dev Guide does a great job of explaining the parameters and providing rather solid examples.

What Aslan did above was to declare a function that gets called when the timer expires. Note that he could also have done this inline as:

CF.activity().scheduleAfter(100,function(){CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME").scheduleActions();
});

or

Declare a function with a parameter and pass the actual widget as 3rd parameter to scheduleAfter which in turn will get passed as w when your function is called.

CF.activity().scheduleAfter (100,function(w){w.scheduleActions();}, CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME"));

Thank you all.
When I first put in the code I used executeActions(). No errors with this.
For reasons discussed on RC and in the Developer's Guide I changed it to scheduleActions() and the error began.

While implementing the changes discussed here I started with:

// INITIALIZE any state tracking variables on boot & ensure all state vars are initialized
function gotoInit() { CF.widget("GOTO", "SAVE_STUFF_HERE", "HOME").scheduleActions(); }
if (System.getGlobal("tv_on") === null) gotoInit();
if (System.getGlobal("zone2on") === null) gotoInit();
if (System.getGlobal("main_zone_on") === null) gotoInit();

Not really elegant but working without errors and "Busy Executing" issues. I realixzed, though I forgot to use the scheduleAfter() but, it seems it's not needed.

scheduleAfter() should, for sure, be used in Page scripts vs using executeActions() on a widget to prevent exceptions/errors as noted in the ProntoScript FAQ.

This is documented here:

[Link: pronto.philips.com]

Note that it is very likely that this is why Widget.scheduleActions() was introduced. I have not tested this but I'm sure this was likely the case.