error: unknown option `--stop-exit-codes'

[KevinWang15]

I wanted to use the Skip Auto Restart For Specific Exit Codes feature, described in https://pm2.keymetrics.io/docs/usage/restart-strategies/

But it is not working

ash-4.4# pm2 --version
5.1.2

ash-4.4# pm2 start ./restore.sh --stop-exit-codes 0
  error: unknown option `--stop-exit-codes'

Please help take a look, thanks.

[zakariamehbi]

Same problem, any news ?

[stefanpl]

Any feedback would be much appreciated ☺️

[rmeghwar]

I am facing the same issue.

[bitBeater]

I have the same issue too

[agniiyer]

Same issue!

[toropigaskunk]

Me too. Any news?

[that1estonian]

It looks like it has never been a actual feature (#5330)

[windowye]

Same issue!

[FaizNL]

Same Issue!

[johhnry]

Same issue here with pm2 5.2.0

pm2 start "ls" --stop-exit-codes 9009

error: unknown option `--stop-exit-codes'

[TotalLag]

issue still exists. can we get a bump on #5330 ?

[taojunnan]

me too

[zx013]

me too, version is 5.2.2

[m-cisse-easy-live]

same issue

[adamgrant-infinitusai]

same issue on 5.3.0

[fiftin]

Same, please update docs if you don't want to implement this feature!!!!

[pmode]

same issue. Or it's a paid tier feature only?

[pstefa1707]

Once upon a time, in a land not so far away, there was a programmer named Paras who was responsible for maintaining a critical service using PM2. Paras was a meticulous coder, but his program had a bug that caused it to crash with a specific exit code. He searched the PM2 documentation and found that the --stop-exit-codes code flag could prevent the program from restarting automatically. "Perfect," he thought, "this will buy me time to fix the issue."

Paras added the flag to his PM2 configuration and ran some tests. To his surprise, the program still restarted after crashing with the designated exit code. He tried different configurations, but nothing seemed to work. He went back to the PM2 documentation and realized that the --stop-exit-codes code flag was only mentioned in the documentation, and not an actual feature of PM2!

Frustrated, he searched online and found a GitHub issue where many others had experienced the same problem. He added his voice to the chorus, hoping for a quick fix. But as time passed, and the issue remained unresolved, he started to lose hope. Over 18 months went by, with many people chiming in, agreeing with him, but nothing changed.

In the end, Paras learned that sometimes even the most well-documented features can be misleading, and sometimes software bugs are harder to fix than they appear. He continued to code, hoping that someday, someone would fix the elusive PM2 bug.

[zhiyuanzhai]

It seems that the feature has been merged (#5330).
However, a new version of PM2 may not be released in a short term according to the version history and the fact that the current version was released just 2 months ago.

[gamersindo1223]

this feature is currently in development:
to install it just use
npm install -g github:Unitech/pm2#development

[MooseV2]

Does anyone have any insight on the pure negligence that must have occurred to have feature docs available and published for something that simply doesn't exist in the master branch?

This issue is over two years old. There are multiple PRs for fixing the issue or fixing the docs. Neither have been released. Unitech has not responded.

Is PM2 production ready or is this really bad product process smell?

[brunosoaresoliveira]

Still a issue on 5.3.0. =[

[futuresymphony]

Bump? Still a problem @Unitech why is this feature contained in the documentation if it is not even a real feature?

[smashah]

Who here wants to make pm3 with me? :P