And just to clarify, is the problem the large number of log messages? Or is your error handling logic not running at all?

In our use case, we have an application that is running a loop to "reconcile" our Pulumi stacks in AWS against incoming change requests We have a loop running in that application that calls

stack.up()

for each stack, which either applies the changes, or does nothing (if no change requests came in) It seems like what we are observing is that if a change request comes in for one of the stacks that causes a

stack.up()

error on that one stack, there are cascading effects on the other stacks — our best guess is that the Pulumi runtime is somehow affected The other "healthy" stacks will run

stack.up()

and output a single generic error at the end that says "one or more errors occurred" If we delete the single stack that we know has an error, then

stack.up()

returns to functioning properly on the other stacks

TL;DR it seems like (our best guess) errors from

stack.up()

are causing wide-ranging problems in our use case, and we're wondering what the best way to catch and handle

stack.up()

errors are

I'll try to adapt the small example above ^ to demonstrate the problem in a loop

Apologies, didn't get sample complete yesterday, will hopefully have small sample to demo problem soon

I guess before I get to that point though, one question: I've added

try

catch

in as many places as I could think to in the

main.js

file above ^ The error output still shows

UnhandledPromiseRejectionWarnings

To phrase my original question better: • What promise isn't being handled? Is it in the

main.js

file somewhere or somewhere in Pulumi SDK?