# general


02/16/2021, 11:30 AM
All the sudden, my TS program started leaking promises. Pretty sure I'm awaiting things properly, let alone it worked just a few hours ago. Network issue?:
Copy code
The Pulumi runtime detected that 5485 promises were still active

at the time that the process exited. There are a few ways that this can occur:

  * Not using `await` or `.then` on a Promise returned from a Pulumi API

  * Introducing a cyclic dependency between two Pulumi Resources

  * A bug in the Pulumi Runtime

Leaving promises active is probably not what you want. If you are unsure about

why you are seeing this message, re-run your program with the `PULUMI_DEBUG_PROMISE_LEAKS`

environment variable. The Pulumi runtime will then print out additional

debug information about the leaked promises.
The debug showed lots of different promises being leaked:
Copy code
CONTEXT: transferIsSecret(resource:cluster-services/nginx-ingress-controller-internal[kubernetes:<|>], roleRef, [object Object])



    at Object.debuggablePromise (/app/services/node_modules/@pulumi/pulumi/runtime/debuggable.js:41:75)

    at Object.transferProperties (/app/services/node_modules/@pulumi/pulumi/runtime/rpc.js:64:322)

    at /app/services/node_modules/@pulumi/pulumi/runtime/resource.js:224:33

    at (<anonymous>)

    at /app/services/node_modules/@pulumi/pulumi/runtime/resource.js:21:71

    at new Promise (<anonymous>)

    at __awaiter (/app/services/node_modules/@pulumi/pulumi/runtime/resource.js:17:12)

    at prepareResource (/app/services/node_modules/@pulumi/pulumi/runtime/resource.js:201:12)

    at Object.registerResource (/app/services/node_modules/@pulumi/pulumi/runtime/resource.js:110:24)

    at new Resource (/app/services/node_modules/@pulumi/pulumi/resource.js:204:24)


02/16/2021, 8:43 PM
This did happen to me once when I lost connectivity to, so it might be a network issue. Can you find any exceptions that aren't about leaked promises? They may lead you closer to the real cause.