René's URL Explorer Experiment


Title: Composite tasks do not notify parent composites · Issue #266 · microsoft/durabletask-python · GitHub

Open Graph Title: Composite tasks do not notify parent composites · Issue #266 · microsoft/durabletask-python

X Title: Composite tasks do not notify parent composites · Issue #266 · microsoft/durabletask-python

Description: WhenAllTask and WhenAnyTask mark themselves complete, but do not notify their parent composite. This means the following orchestration does not resume when all activities complete: all_task = task.when_all(activity_tasks) winner = yield ...

Open Graph Description: WhenAllTask and WhenAnyTask mark themselves complete, but do not notify their parent composite. This means the following orchestration does not resume when all activities complete: all_task = task....

X Description: WhenAllTask and WhenAnyTask mark themselves complete, but do not notify their parent composite. This means the following orchestration does not resume when all activities complete: all_task = task....

Opengraph URL: https://github.com/microsoft/durabletask-python/issues/266

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Composite tasks do not notify parent composites","articleBody":"`WhenAllTask` and `WhenAnyTask` mark themselves complete, but do not notify their parent composite.\n\nThis means the following orchestration does not resume when all activities complete:\n\n```python\nall_task = task.when_all(activity_tasks)\nwinner = yield task.when_any([cancel_task, all_task])\n```\n\nA current workaround is to wait for each leaf task with repeated `when_any` calls. The workaround preserves cancellation, but Durable Task Scheduler no longer shows the standard **Fan-out** group.\n\nCould composite completion propagate to the parent in the same way that `CompletableTask.complete()` does?\n\nA regression test can compose `when_any([cancel, when_all([a, b])])`, complete `a` and `b`, and verify that the outer task completes with the inner `when_all` task.\n\r\n## Compatibility and behavior-change considerations\r\n\r\nPR #267 fixes the missing completion propagation unconditionally. The proposed\r\ndirection is to accept this intentional replay-compatibility break rather than\r\npreserve the bug, provided the affected scenarios and upgrade guidance are\r\nexplicit. This is a behavioral/replay change, not a public signature change or\r\na new abstract-method requirement for third-party subclasses.\r\n\r\n### Affected histories\r\n\r\nAn existing instance can have a history like this:\r\n\r\n1. `when_any([cancel, when_all(tasks)])` is pending.\r\n2. All activities finish, but the inner `when_all` does not notify the race.\r\n3. A later cancellation wins, and the orchestration records cancellation-branch\r\n   work, for example a `cleanup` activity.\r\n4. After upgrading, replay completes the inner composite at step 2 and takes the\r\n   success branch instead. If that branch schedules `finish` where history\r\n   recorded `cleanup`, replay fails with `NonDeterminismError`.\r\n\r\n> [!WARNING]\r\n> A changed replay is not guaranteed to raise `NonDeterminismError`. If both\r\n> branches schedule the same activity name/ID but use different inputs or local\r\n> continuation state, the executor can accept the recorded action and continue\r\n> with the new branch. An old history using `record(\"cleanup\")` was reproduced\r\n> completing with `\"cleanup\"` on the merge base and `\"finish\"` with the fix.\r\n> Do not rely on nondeterminism errors alone to identify affected instances.\r\n\r\nThis is not a blanket break for all orchestrations. Ordinary non-nested\r\ncomposites retain their behavior. A cancellation-first history for the example\r\nabove still replays consistently. A history still blocked at the nested\r\ncomposite, with no conflicting downstream continuation, can regain progress\r\nwhen the orchestration next executes. Deploying the fix alone does not\r\nnecessarily wake an otherwise idle instance.\r\n\r\n### Provider and deployment implications\r\n\r\nBoth `durabletask.azuremanaged` and `azure-functions-durable` v2 use the core\r\nimplementation, including the Functions compatibility APIs `context.task_all()`\r\nand `context.task_any()`. Their current core constraints are open-ended:\r\n`durabletask>=1.10.1` and `durabletask[opentelemetry]>=1.10.1`, respectively.\r\nPinning only the provider therefore does not freeze this behavior; a fresh\r\ndependency resolution can pick up the correction without a provider-version\r\nchange. A core major-version bump alone would not protect those existing\r\nprovider constraints.\r\n\r\n- Pin or lock the core `durabletask` version until the transition is deliberate.\r\n- Let affected running instances finish on the previous SDK, or retain the old\r\n  deployment/task hub and use a separate task hub for new instances.\r\n- Avoid mixing old and corrected workers on the same affected task hub during\r\n  the transition. Stuck instances may require deliberate recovery rather than\r\n  simply waiting to drain.\r\n- Keep the warnings in all three package changelogs and carry them into release\r\n  notes, including upgrades from earlier Functions v2 prereleases. Coordinate\r\n  package/dependency version changes in the release PR, not this fix.\r\n\r\n### PR scope and regression coverage\r\n\r\nThe latest PR already includes replay warnings in all three changelogs. The\r\nimplementation preserves result ordering, waits for all `when_all` children\r\nbefore surfacing failure, and notifies a `when_any` parent only for the first\r\nwinner. No additional public API or minimum-Python-version change is needed.\r\n\r\nThe new tests exercise task objects directly. An executor-level regression\r\nwould additionally preserve the intended scheduling/replay boundary: successful\r\nnested completion, replay of a history written by the corrected implementation,\r\nand an unchanged cancellation-first history. The legacy-history mismatch above\r\nis also useful to encode as an intentional compatibility test.\r\n\r\nThe automated review's empty-`when_all([])` concern reproduces on both the merge\r\nbase and the PR. It is a pre-existing empty-input behavior, not a regression\r\nintroduced by completion propagation. Keep any empty-input semantic change\r\nseparate rather than silently expanding this fix.\r\n","author":{"url":"https://github.com/TsuyoshiUshio","@type":"Person","name":"TsuyoshiUshio"},"datePublished":"2026-09-14T21:37:07Z","url":"https://github.com/microsoft/durabletask-python/issues/266"}

react-profiling0
react-import-mapreact,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322
route-pattern/_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format)
route-controllervoltron_issues_fragments
route-actionissue_layout
fetch-noncev2:2231a630-5a47-dcba-e4db-8535386db8e7
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idA57A:3F8062:4E492:68171:6AFE2CDD
html-safe-noncebc1c2a50b55ab64442ba7c75b2db21caa2c26627b50791b259e95d1c91bf43bf
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNTdBOjNGODA2Mjo0RTQ5Mjo2ODE3MTo2QUZFMkNERCIsInZpc2l0b3JfaWQiOiI4MTA3MjQ4NTY4Mjk0NTgzNTE4IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmacf0c7f52ec8e41441823c2395036fe29698b09f174f82f113a103969f5150501a
hovercard-subject-tagissue:5454871776
github-keyboard-shortcutsrepository,issues,copilot
google-site-verificationApib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I
octolytics-urlhttps://collector.github.com/github/collect
analytics-location///voltron/issues_fragments/issue_layout
fb:app_id1401488693436528
apple-itunes-appapp-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/microsoft/durabletask-python/266/issue_layout
twitter:imagehttps://opengraph.githubassets.com/5b0da73185302c2426dcf2b4513e7250eed839633949ed7af629cc0b18fba2a3/microsoft/durabletask-python/issues/266
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/5b0da73185302c2426dcf2b4513e7250eed839633949ed7af629cc0b18fba2a3/microsoft/durabletask-python/issues/266
og:image:altWhenAllTask and WhenAnyTask mark themselves complete, but do not notify their parent composite. This means the following orchestration does not resume when all activities complete: all_task = task....
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameTsuyoshiUshio
hostnamegithub.com
expected-hostnamegithub.com
Nonee973f9ec3625f3faad8cac5c2d11a214b7ffe45f3cc563b828459b290ecaeed3
turbo-cache-controlno-preview
go-importgithub.com/microsoft/durabletask-python git https://github.com/microsoft/durabletask-python.git
octolytics-dimension-user_id6154722
octolytics-dimension-user_loginmicrosoft
octolytics-dimension-repository_id627664515
octolytics-dimension-repository_nwomicrosoft/durabletask-python
octolytics-dimension-repository_publictrue
octolytics-dimension-repository_is_forkfalse
octolytics-dimension-repository_network_root_id627664515
octolytics-dimension-repository_network_root_nwomicrosoft/durabletask-python
turbo-body-classeslogged-out env-production page-responsive
disable-turbofalse
browser-stats-urlhttps://api.github.com/_private/browser/stats
browser-errors-urlhttps://api.github.com/_private/browser/errors
release1f92c367595b9190e0be293896078033886b1913
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/microsoft/durabletask-python/issues/266#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fdurabletask-python%2Fissues%2F266
GitHubRepository hosting, code review, and collaborationhttps://github.com/platform
CopilotAI coding agent for tasks, projects, and automated workhttps://github.com/features/copilot
ActionsCI/CD and automationhttps://github.com/features/actions
Code QualityQuality analysis, fixes, and enforcementhttps://github.com/features/code-quality
CodespacesCloud development environmentshttps://github.com/features/codespaces
Code SecurityVulnerability detection and remediationhttps://github.com/security/advanced-security/code-security
Secret ProtectionSecret scanning and leak preventionhttps://github.com/security/advanced-security/secret-protection
All Featureshttps://github.com/features
Documentationhttps://docs.github.com/en
Traininghttps://learn.github.com/skills
Certificationshttps://learn.github.com/credentials
Build with Copilothttps://github.com/features/ai
Customize Copilothttps://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-copilot-overview
Integrationshttps://github.com/marketplace
Trending reposhttps://github.com/trending
GitHub Sponsorshttps://github.com/open-source/sponsors
Developer articleshttps://github.com/resources/articles
ChangelogYour source for the latest features, improvements, and fixes across GitHub products, all in one place.https://github.blog/changelog/
Enterpriseshttps://github.com/enterprise
Teamhttps://github.com/team
Startupshttps://github.com/enterprise/startups
Nonprofitshttps://github.com/solutions/industry/nonprofits
Healthcarehttps://github.com/solutions/industry/healthcare
Financial serviceshttps://github.com/solutions/industry/financial-services
Manufacturinghttps://github.com/solutions/industry/manufacturing
Governmenthttps://github.com/solutions/industry/government
See all industrieshttps://github.com/solutions/industry
Why GitHubhttps://github.com/why-github
Customer Storieshttps://github.com/customer-stories
Business insightshttps://github.com/solutions/executive-insights
Trust Centerhttps://github.com/trust-center
GitHub Advanced SecurityEnterprise-grade code securityhttps://github.com/security/advanced-security
Copilot for businessEnterprise-grade AI featureshttps://github.com/features/copilot/copilot-business
Premium SupportEnterprise-grade 24/7 supporthttps://github.com/enterprise/premium-support
Documentationhttps://docs.github.com/en
Resource centerhttps://github.com/resources
Bloghttps://github.blog/
Events & webinarshttps://github.com/resources/events
Community Forumhttps://github.com/orgs/community/discussions
Customer Storieshttps://github.com/customer-stories
Integrationshttps://github.com/marketplace
Customer supporthttps://help.github.com/
Traininghttps://learn.github.com/skills
GitHub Statushttps://www.githubstatus.com/
Abouthttps://github.com/about
Partnershttps://github.com/partners
Changeloghttps://github.blog/changelog/
GitHub UniverseThe event for developers, by developers — talks, workshops, and what’s next for GitHub.https://githubuniverse.com/
Pricinghttps://github.com/pricing
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fdurabletask-python%2Fissues%2F266
Sign uphttps://github.com/signup?ref_cta=Sign+up&ref_loc=header+logged+out&ref_page=%2F%3Cuser-name%3E%2F%3Crepo-name%3E%2Fvoltron%2Fissues_fragments%2Fissue_layout&source=header-repo&source_repo=microsoft%2Fdurabletask-python
Reloadhttps://github.com/microsoft/durabletask-python/issues/266
Reloadhttps://github.com/microsoft/durabletask-python/issues/266
Reloadhttps://github.com/microsoft/durabletask-python/issues/266
microsofthttps://github.com/microsoft
durabletask-pythonhttps://github.com/microsoft/durabletask-python
Codehttps://github.com/microsoft/durabletask-python
Issues15 (15)https://github.com/microsoft/durabletask-python/issues
Pull requests12 (12)https://github.com/microsoft/durabletask-python/pulls
Actionshttps://github.com/microsoft/durabletask-python/actions
Projectshttps://github.com/microsoft/durabletask-python/projects
Security and qualityhttps://github.com/microsoft/durabletask-python/security
Insightshttps://github.com/microsoft/durabletask-python/insights
https://github.com/microsoft/durabletask-python
New issuehttps://github.com/login?return_to=https://github.com/microsoft/durabletask-python/issues/266
New issuehttps://github.com/login?return_to=https://github.com/microsoft/durabletask-python/issues/266
#267https://github.com/microsoft/durabletask-python/pull/267
Composite tasks do not notify parent compositeshttps://github.com/microsoft/durabletask-python/issues/266#top
#267https://github.com/microsoft/durabletask-python/pull/267
https://github.com/TsuyoshiUshio
Tsuyoshi Ushio (TsuyoshiUshio)https://github.com/TsuyoshiUshio
on Sep 14, 2026https://github.com/microsoft/durabletask-python/issues/266#issue-5454871776
#267https://github.com/microsoft/durabletask-python/pull/267
andystapleshttps://github.com/andystaples
completedhttps://github.com/microsoft/durabletask-python/issues?q=is%3Aissue%20state%3Aclosed%20archived%3Afalse%20reason%3Acompleted
#267https://github.com/microsoft/durabletask-python/pull/267
on Sep 28, 2026https://github.com/microsoft/durabletask-python/issues/266#event-32023620145
Sign up for freehttps://github.com/signup?return_to=https://github.com/microsoft/durabletask-python/issues/266
Sign in to commenthttps://github.com/login?return_to=https://github.com/microsoft/durabletask-python/issues/266
https://github.com
Termshttps://docs.github.com/site-policy/github-terms/github-terms-of-service
Privacyhttps://docs.github.com/site-policy/privacy-policies/github-privacy-statement
Securityhttps://github.com/security
Statushttps://www.githubstatus.com/
Communityhttps://github.community/
Docshttps://docs.github.com/
Contacthttps://support.github.com?tags=dotcom-footer

Viewport: width=device-width


URLs of crawlers that visited me.