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

i'm using pulumi in CI, in a pipeline where i have nightly, staging, and prod jobs. the staging job triggers after nightly finishes, and i'd expected that once a `pulumi up` has finished, it unlocks the stack. this doesn't seem to be the case; the staging job gets a 409 error. is this a bug, or a known problem with <http://app.pulumi.com|app.pulumi.com>'s concurrency management?

That is not expected behavior, no. Not a known problem either.

Can you share the full error output you're getting? Are your nightly, staging, and prod jobs using different stacks?