pullAndReload call stops my application and reloads the caller module instead

Issue

When using the module pm2-auto-pull, which makes a pm2.pullAndReload call, it pulls the correct repo, but it starts the module a second time instead of the application I am running. It just flat out stops the newly pulled application.

I have written my own module to test pullAndReload and I am getting the same behavior.

Log output

PM2: 2016-07-08 12:27:02: [PM2][WORKER] Started with refreshing interval: 30000
PM2: 2016-07-08 12:27:22: Starting execution sequence in -fork mode- for app name:MYAPP id:0
PM2: 2016-07-08 12:27:22: App name:MYAPP id:0 online
PM2: 2016-07-08 12:27:44: Starting execution sequence in -fork mode- for app name:pm2-auto-pull id:1
PM2: 2016-07-08 12:27:44: App name:pm2-auto-pull id:1 online
PM2: 2016-07-08 12:29:21: Process 0 in a stopped status, starting it
PM2: 2016-07-08 12:29:21: Stopping app:MYAPP id:0
PM2: 2016-07-08 12:29:21: App [MYAPP] with id [0] and pid [27333], exited with code [0] via signal [SIGINT]
PM2: 2016-07-08 12:29:21: Starting execution sequence in -fork mode- for app name:pm2-auto-pull id:1
PM2: 2016-07-08 12:29:21: App name:pm2-auto-pull id:1 online

Reproduce the behavior using pm2-auto-pull and the pullAndReload call, then compare the log sequence for MYAPP and pm2-auto-pull. Trace why the caller module is started again and the newly pulled application is stopped; done means pullAndReload reloads the intended application without restarting the caller module.