Hello. I have an automation app that some times ends up in a weird state and wonder if anyone might know what happens? If our automation project fails once to update a stack all the updates to the same stack after that will end with

"One or more errors occurred"

Even though everything has succeeded. If I restart the application it works just fine and the message disappear, which I find pretty strange.

Which automation SDK (go, node, etc)?

node

Ideally the pulumi client should be "stateless",

Ah it's not. If your using inline stacks there is global state inside the pulumi node sdk so you can't run operations in parallel.

ok, so that explains the first part of why I can experience what I see, that is, if it fails one time the next can also fail... but it doesn't explain why I do get the error even though everything has succeeded.

Not having the state as a global in the SDK would require a large api change to pass the deployment context through everywhere (because node doesn't have async locals). The go SDK is written like this, maybe 4.0 we could revisit it.

That's fine, but I still don't understand why I get an "One or more errors occurred" even though all the resources have been provisioned, and that it only happens after on deploy has failed first.

My guess is that the async tracking the engine does is picking up some left over asyncs from the first update and thinking their part of the other updates. Do you get any more logs than just "One or more errors occurred"?

That is the only log I get, so it is quite hard to debug. I do think I am awaiting all async, but must be missing something.

Just to check this is with the nodejs automation api and using inline programs?

yes, it is with an inline program using the nodejs api

hmm odd, I’ll see if we can repro it

I can check if I can make a smaller repro as well.