No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Hello again, I’m sorry to ask another question, is a long time I wanted to ask.
I’m using Nodejs

When I run a `stack.up` even if that instruction is within a `try catch` block if the pulumi program throws an exception, there’s no way to get handled by the surrounding `try catch`  block and the process fails making the POD process to restart.

The error is something like this
```{"level":50,"time":1677281160538,"pid":7,"hostname":"abcdef-8b8444bd5-lqb7j","err":{"type":"CommandError","message":"code: -2
 stdout: 
 stderr: Command failed with exit code 255: pulumi up --yes --skip-preview --client=127.0.0.1:43037 --exec-kind auto.inline --stack mystack --non-interactive```
Is there a better way to handle and catch in the code this kind of error in preventing the POD process to restart?

Thanks a lot for your precious help