René's URL Explorer Experiment


Title: RetryPolicy max_retry_interval does not prevent backoff overflow, failing capped retries · Issue #367 · microsoft/durabletask-python · GitHub

Open Graph Title: RetryPolicy max_retry_interval does not prevent backoff overflow, failing capped retries · Issue #367 · microsoft/durabletask-python

X Title: RetryPolicy max_retry_interval does not prevent backoff overflow, failing capped retries · Issue #367 · microsoft/durabletask-python

Description: Summary RetryPolicy.max_retry_interval does not prevent exponential-backoff overflow. RetryableTask.compute_next_delay() computes math.pow(coefficient, attempt - 1) before applying the configured cap. Once the intermediate power overflow...

Open Graph Description: Summary RetryPolicy.max_retry_interval does not prevent exponential-backoff overflow. RetryableTask.compute_next_delay() computes math.pow(coefficient, attempt - 1) before applying the configured c...

X Description: Summary RetryPolicy.max_retry_interval does not prevent exponential-backoff overflow. RetryableTask.compute_next_delay() computes math.pow(coefficient, attempt - 1) before applying the configured c...

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

X: @github

direct link

Domain: github.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"RetryPolicy max_retry_interval does not prevent backoff overflow, failing capped retries","articleBody":"## Summary\n\n`RetryPolicy.max_retry_interval` does not prevent exponential-backoff overflow. `RetryableTask.compute_next_delay()` computes `math.pow(coefficient, attempt - 1)` before applying the configured cap. Once the intermediate power overflows, the worker fails the orchestration with `OverflowError` instead of continuing bounded retries or delivering the original exhausted failure to the orchestrator.\n\nThis reproduces with the normal coefficient `2.0`, a 1ms maximum interval and 1,027 maximum attempts: the orchestration fails after 1,025 activity calls. The cap has already made the delay constant, but the unused intermediate power keeps growing. A large coefficient below accelerates the same failure to three calls.\n\nThis is a local SDK reproduction using the public in-memory testing backend, client and worker. No Azure account or service was used, and no production incident is claimed.\n\n## Reproduction\n\nRun against core `durabletask` 1.13.1 from current main `256ffbdca1fb97f5ed96e547810b5d63ebefaabe` with its runtime dependencies installed:\n\n```python\nimport logging\nimport socket\nfrom datetime import timedelta\nfrom durabletask import client, task, worker\nfrom durabletask.testing import create_test_backend\nlogging.basicConfig(level=logging.ERROR)\nwith socket.socket() as s:\n    s.bind(('127.0.0.1',0))\n    port=s.getsockname()[1]\nhost=f'localhost:{port}'\nb=create_test_backend(port=port)\ncalls=[]\ndef fail(ctx,_):\n    calls.append(True)\n    raise ValueError('downstream unavailable')\ndef orchestration(ctx,_):\n    policy=task.RetryPolicy(first_retry_interval=timedelta(milliseconds=1),max_number_of_attempts=5,\n                            backoff_coefficient=1e200,max_retry_interval=timedelta(milliseconds=1))\n    try:\n        yield ctx.call_activity(fail,retry_policy=policy)\n    except task.TaskFailedError:\n        return 'handled expected downstream failure'\ntry:\n    with worker.TaskHubGrpcWorker(host_address=host) as w:\n        w.add_orchestrator(orchestration)\n        w.add_activity(fail)\n        w.start()\n        with client.TaskHubGrpcClient(host_address=host) as c:\n            id=c.schedule_new_orchestration(orchestration)\n            state=c.wait_for_orchestration_completion(id,timeout=10)\n            print('status:',state.runtime_status)\n            print('activity calls:',len(calls))\n            print('output:',state.serialized_output)\n            print('failure:',state.failure_details)\nfinally:\n    b.stop()\n    b.reset()\n```\n\nActual: `status: FAILED`, `activity calls: 3`, no output, and failure type `builtins.OverflowError` with message `math range error` at `math.pow(...)` in `compute_next_delay()`.\n\nExpected: five calls at delays no greater than 1ms, followed by the orchestrator's `TaskFailedError` handler returning `handled expected downstream failure` and a `COMPLETED` instance. With `backoff_coefficient=1.0`, that control does complete with five calls.\n\nFor the normal-coefficient case, change `backoff_coefficient` to `2.0`, `max_number_of_attempts` to `1027` and the completion timeout to `60`. I ran this separately on Python 3.13: it fails after 1,025 calls with the same SDK overflow rather than reaching the configured attempt limit. The local run completed in about 31 seconds; timing is not a benchmark or a guarantee.\n\n## Validation\n\nLinux x86_64, CPython 3.11 and 3.13, independently:\n\n- Unmodified native orchestration-executor, task-composition, retry-timeout and failure-details suites: **344 passed** on each interpreter.\n- Twelve focused delay-calculation cases: **8 fail, 4 pass as controls**. Failing cases include coefficients 2, 10, 1000 and the accelerated large coefficient, with positive and zero caps.\n- Four public client/worker cases: **2 fail, 2 pass as controls**. Both activity and sub-orchestration retries fail for the accelerated overflow case; the constant-backoff versions exhaust normally and are caught by the parent.\n- The 1,025-call coefficient-2 public activity run was executed on Python 3.13 only.\n\nNo full repository/provider suite, hosted CI, Azure emulator or live-service validation is claimed. No production fix has been written or submitted.\n\n## Scope and compatibility\n\nI checked #96/#116 (absent maximum interval) and #316/#326 (retry-timeout logical clock); neither fixes capped-power overflow. The current open async stack retains this delay calculation too. The intended scope would be to avoid evaluating an already-saturated power while preserving attempt limits, timeout checks and ordinary delay rounding.\n\nCorrecting the failure can change replay behavior for histories that previously terminated with this overflow, so any eventual patch needs an explicit compatibility decision and upgrade guidance. I will wait for maintainer triage/discussion before preparing a PR. Would this focused capped-backoff fix be welcome?\n\nInvestigation and reproduction tests developed with AI assistance. The reproduction runs above were executed and their outputs inspected.","author":{"url":"https://github.com/Rajatendu1","@type":"Person","name":"Rajatendu1"},"datePublished":"2026-11-17T08:41:02Z","url":"https://github.com/microsoft/durabletask-python/issues/367"}

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:3b3d7652-850f-4061-f473-1ea04e80c283
current-catalog-service-hash81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114
request-idA7D8:355A02:676CC:8AED2:6AFE1E85
html-safe-nonce3aab22c5ba1a390a273a29ad6c544cd3d2f2984a9a97a8dd8d23fc4adc488063
visitor-payloadeyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBN0Q4OjM1NUEwMjo2NzZDQzo4QUVEMjo2QUZFMUU4NSIsInZpc2l0b3JfaWQiOiI3MDIxMTE5NzA2NDI1NTk3NTczIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0=
visitor-hmac243e00e4de00240ac1cfc35ea5e2ddc5c1f068667a53950a2c0913d7ceaa4879
hovercard-subject-tagissue:6440716844
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/367/issue_layout
twitter:imagehttps://opengraph.githubassets.com/e2d340023d6f310ecc9af1efacd8a717f105985ee9354e3ffdbc8b8d0c62c7ce/microsoft/durabletask-python/issues/367
twitter:cardsummary_large_image
og:imagehttps://opengraph.githubassets.com/e2d340023d6f310ecc9af1efacd8a717f105985ee9354e3ffdbc8b8d0c62c7ce/microsoft/durabletask-python/issues/367
og:image:altSummary RetryPolicy.max_retry_interval does not prevent exponential-backoff overflow. RetryableTask.compute_next_delay() computes math.pow(coefficient, attempt - 1) before applying the configured c...
og:image:width1200
og:image:height600
og:site_nameGitHub
og:typeobject
og:author:usernameRajatendu1
hostnamegithub.com
expected-hostnamegithub.com
Noned0525ab1464526bf4532a5551aa348cf100dff75ef808a96fc67a08b1d946aa9
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
releasefef3993a71fa20f7be8e167132fbf9619bc66e12
ui-targetfull
theme-color#1e2327
color-schemelight dark
react-app-nameissues

Links:

Skip to contenthttps://github.com/microsoft/durabletask-python/issues/367#start-of-content
https://github.com/
Sign inhttps://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fdurabletask-python%2Fissues%2F367
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%2F367
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/367
Reloadhttps://github.com/microsoft/durabletask-python/issues/367
Reloadhttps://github.com/microsoft/durabletask-python/issues/367
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/367
New issuehttps://github.com/login?return_to=https://github.com/microsoft/durabletask-python/issues/367
RetryPolicy max_retry_interval does not prevent backoff overflow, failing capped retrieshttps://github.com/microsoft/durabletask-python/issues/367#top
https://github.com/Rajatendu1
Rajatendu Dey (Rajatendu1)https://github.com/Rajatendu1
on Nov 17, 2026https://github.com/microsoft/durabletask-python/issues/367#issue-6440716844
#96https://github.com/microsoft/durabletask-python/issues/96
#116https://github.com/microsoft/durabletask-python/pull/116
#316https://github.com/microsoft/durabletask-python/issues/316
#326https://github.com/microsoft/durabletask-python/pull/326
Sign up for freehttps://github.com/signup?return_to=https://github.com/microsoft/durabletask-python/issues/367
Sign in to commenthttps://github.com/login?return_to=https://github.com/microsoft/durabletask-python/issues/367
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.