1.14.0

New Features

Workflow Debouncing. When you debounce a workflow, you delay its execution until some time has passed since the workflow has last been called. Debouncing is really useful for preventing wasted work when a workflow may be triggered multiple times in quick succession. For example, if a user is editing an input field, you can debounce their changes to execute a processing workflow only after they haven't edited the field for some time.

Docs: https://docs.dbos.dev/python/reference/contexts#debouncing

What's Changed

• Debouncing by @kraftp in #455
• Fix Tests by @kraftp in #448
• fix(client): Await for a coroutine in retrieve_workflow_async() by @korya in #449
• Fix destroy for asyncio by @qianl15 in #451
• Use to_thread for sync transaction functions by @qianl15 in #454
• Correctly trace OTLP spans by @qianl15 in #457
• Update Debouncer Tests by @kraftp in #460
• Fix Stream Recovery by @kraftp in #461
• Update Debouncer API by @kraftp in #462

New Contributors

• @korya made their first contribution in #449

Full Changelog: 1.13.0...1.14.0