session {} not running second module

[Alan DeKok]

> On Mar 16, 2017, at 3:36 PM, Matt Nelson - Silverark <matt.nelson at silverark.co.uk> wrote:
> 
> 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

  Don't do that.  It's not supported, and was never intended to work.

  You're using a VERY old version of the server.  When you upgrade, this incorrect configuration will stop working.

  Alan DeKok.