Handling unresolved promises when a workflow completes
Open
@VaguelySerious is already working on this.
Since Nov 4, 2025.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 365
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 169
Description
Right now we don't have proper handling for promises/steps/sleeps/hooks etc. that are left unresolved when the workflow completes. We need to document and properly implement the right behaviour here. @TooTallNate and I have some thoughts here- will document this later
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.