temporalio / temporalio/temporal

Carryover instead of reject incoming signals upon continueAsNew

Open
#8,097 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
23.2k
Forks
1.9k
Avg merge
2d 8h
Merged PRs (30d)
228

Description

Is your feature request related to a problem? Please describe.
Right now we reject new incoming signals if workflow attempts to close/continueAsNew but fails due to buffered signals (or other events) to prevent an infinite loop.

This makes sense for completing/failing the workflow but not so much for continueAsNew.

Describe the solution you'd like
Upon continueAsNew, we can simply flush buffered signals to the new run instead of current run, and we don't have to fail & retry the workflow task

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by tracing continueAsNew handling and the path that rejects incoming signals when buffered events prevent completion; done means buffered signals are carried into the new run without failing and retrying the workflow task.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.