Skip to content

Batch workflow activations across language SDKs - #1664

Closed
eamsden wants to merge 8 commits into
eamsden/disable-workflow-task-chunkingfrom
eamsden/workflow-activation-batches
Closed

eamsden wants to merge 8 commits into
eamsden/disable-workflow-task-chunkingfrom
eamsden/workflow-activation-batches

Conversation

@eamsden

@eamsden eamsden commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

What was changed

Require activation batches and indexed completion batches across Core, the Rust SDK, and the C bridge. Core supplies the continuation policy and batches replay from available history, retaining singleton batches where needed.

Stacked on #1659 at 149931194. Rebased to preserve workflow-start-only chunking selection and internal handling of jobless tasks.

Why?

Reduce Core/language round trips while preserving activation boundaries, replay checks, and history recording. Batching applies independently of chunking.

Checklist

  1. Closes: N/A.
  2. How was this tested: Core and Rust SDK unit suites with the chunking feature enabled and disabled; 12 timer integration tests in each configuration; feature-enabled rejected-update replay (2), history compatibility (2), and external storage tests (17); formatting, cargo lint, cargo test-lint, and cargo changelog-check. The existing port-binding unit test failed with AddrInUse; unit suites passed with that test excluded. Full integration suites were not run.
  3. Any docs updates needed? Updated protocol and API documentation, README, and changelogs.

@eamsden
eamsden force-pushed the eamsden/workflow-activation-batches branch from 7525bb3 to c94e9a7 Compare October 16, 2026 00:03
@eamsden
eamsden added this pull request to stack #1665 October 16, 2026 00:12
@Sushisource
Sushisource force-pushed the eamsden/workflow-activation-batches branch from c94e9a7 to e2984fc Compare November 17, 2026 00:24
@Sushisource

Copy link
Copy Markdown
Member

I am closing this because I don't think the complexity is worth it. There is only one remaining pathological case where un-chunked can cause significant increase in replay time: When history consists of many many sections in a row that look specifically like:

WFT Scheduled
Signal
WFT Started
WFT Completed
// no jobs

Note that, importantly, the signal has to be after scheduled but before started which is highly unusual in the real world.

The only other situation would be a sequence of totally empty tasks, as in LA heartbeating, but the un-chunking PR deals with this by simply not waking on empty activations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants