Skip to content

Apply activation jobs before running workflow tasks - #2148

Draft
VegetarianOrc wants to merge 2 commits into
mainfrom
amazzeo/workflow-activation-batch-only
Draft

VegetarianOrc wants to merge 2 commits into
mainfrom
amazzeo/workflow-activation-batch-only

Conversation

@VegetarianOrc

@VegetarianOrc VegetarianOrc commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

What was changed

Add the internal APPLY_ACTIVATION_JOBS_BEFORE_RUNNING_TASKS flag (3). It applies all jobs in an activation before running workflow tasks, without enabling the cancellation changes bundled into PROCESS_WORKFLOW_ACTIVATION_JOBS_AS_SINGLE_BATCH (2). The new flag is off by default, and replay continues to use the behavior recorded in history.

Why?

Workers need a way to opt into batched job processing without also opting into different cancellation semantics. The original flag keeps its existing behavior for replay compatibility.

Checklist

  1. Closes: N/A.

  2. How was this tested:

    • Replay tests verify legacy and single-batch scheduling order.
    • A child-completion race verifies that batching alone does not change cancellation handling.
    • Full poe test suite on the stack tip (Python 3.12.13): 1,892 passed, 10 skipped.
  3. Any docs updates needed? No. This is an internal flag and does not change the default behavior.

@VegetarianOrc VegetarianOrc changed the title amazzeo/workflow activation batch only Apply activation jobs before running workflow tasks Nov 19, 2026

This branch has not been deployed

No deployments
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.

1 participant