Heroku applications do not work forever script.js

Question

I have a heroku application created on my local system and pushing it towards a hero, then I launched

heroku run node_modules/forever/bin/forever start server.js

and I got this answer -

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: server.js

and after that if I run

heroku run node_modules/forever/bin/forever list

I got -

Running `node_modules/forever/bin/forever list` attached to terminal... up, run.5132
info:    No forever processes running

and in heroku magazines there is -

Starting process with command `node_modules/forever/bin/forever start server.js` by [e-mail]
2014-07-05T17:24:54.833343+00:00 heroku[run.5098]: State changed from starting to up
2014-07-05T17:24:58.695683+00:00 heroku[run.5098]: State changed from up to complete
2014-07-05T17:24:58.689043+00:00 heroku[run.5098]: Process exited with status 0

and my server.js has -

var async = require('async');
var shell = require('shelljs');

async.parallel([
        async.apply(shell.exec, './collect1.sh'),
        async.apply(shell.exec, './collect2.sh'),
        async.apply(shell.exec, './collect3.sh'),
        async.apply(shell.exec, './collect4.sh'),
        async.apply(shell.exec, './collect5.sh'),
        async.apply(shell.exec, './mi2.sh'),
    ],
    function (err, results) {
        console.log(results);
    });

and these shell scripts are long executable files with a huge amount of delay, but the logs say that the state is from completion to the end, but I don’t understand why, since in my local system it creates more processes and wait states, and it starts perfectly therefore, the heroic this does not allow, or I'm wrong here.