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

Hi! I have a question: I am currently using the automation API to run Pulumi stuff. But sometimes it will fail, which can happen because the Dockerfile wasn't right or the user didn't have the appropriate rights. This is okay but then when I want to re-run the code it fails with:

```oncurrentUpdateError: code: -2
 stdout:
 stderr: Command failed with exit code 255: pulumi refresh --yes --skip-preview --exec-kind auto.inline --stack pulumi-demo --non-interactive
warning: A new version of Pulumi is available. To upgrade from version '3.55.0' to '3.58.0', run
   $ brew upgrade pulumi
or visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.
error: the stack is currently locked by 1 lock(s).  ```
Then I have to manually fix this by running `pulumi cancel`. Is there a way to handle this in the code that when the pulumi operation fails to gracefully exit the process, so it doesn't stay locked?