Re: session {} not running second module

16 Mar 2017

      Hello All,

Please disregard my last email. I think I've solved it. The debugging 
showed me the update in the session code I posted returned noop, so noop 
must equal return! I added noop=1 and it kept me in the group. Just took 
a while to get my head around how the group bit works. Didn't realise 
the update request returned a code too, it must be numeric rather than 
return in the accounting section that's why it kept me in there.

if(config:User-Name) {
     noop=1
     update request {
         User-Name := config:User-Name
     }
}

Thanks, Matt

Re: session {} not running second module

Matt Nelson - Silverark