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

`pulumi cancel` cancels the update that’s in progress

we should probably explain that in the error message

Well, to be clear, the _usual_ solution is to wait until the other update is done... :slightly_smiling_face:

`pulumi cancel` is really a last resort, since if the update failed gracefully (i.e., not a Pulumi bug), it almost never gets left in this state.

That’s true, but I think we could still improve the error message

I am actually wondering, <@UD2HJDBCL> do you know how the stack got into this state? Did `cancel` do the trick?

I ask because normally this just means you have a concurrent update running somewhere. Cancelling it can have adverse implications. This coupled with the fact that you really ought not to need to use it other than for Pulumi bugs is why we don't advertise it.

If it's just a concurrent update, <@U83S3MLQ0> were discussing this in the morning today, and it's clear we need a better solution. I'll file an issue momentarily.

<@U84SY03DF> forcefully closed it, used `update` instead of `preview` on production :grin:

Great, thanks -- filed <https://github.com/pulumi/pulumi/issues/2073> to do better here.