Open drewhoskins-temporal opened 2 months ago
Same for child workflows (at least starting), external signals, nexus, and any other async thing a user should not be abandoning the response to. Things like timers make more sense to trivially abandon. An argument could be made for doing this for all coroutines, but that may be a bit cumbersome for users doing background work (though there is precedent in language runtimes about unresolved promises or unawaited tasks and such).
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
We're adding warnings when signals and updates dangle after the workflow closes or continues as new. We should consider providing a similar warning when activities dangle.
Additional context
Per-SDK Tickets