pyworkflow-engine 0.2.14__tar.gz → 0.2.15__tar.gz

{pyworkflow_engine-0.2.14 → pyworkflow_engine-0.2.15}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pyworkflow-engine
-Version: 0.2.14
+Version: 0.2.15
 Summary: A Python implementation of durable, event-sourced workflows inspired by Vercel Workflow
 Author: PyWorkflow Contributors
 License: MIT

{pyworkflow_engine-0.2.14 → pyworkflow_engine-0.2.15}/pyproject.toml

@@ -7,7 +7,7 @@ packages = [{include = "pyworkflow"}]
 
 [project]
 name = "pyworkflow-engine"
-version = "0.2.14"
+version = "0.2.15"
 description = "A Python implementation of durable, event-sourced workflows inspired by Vercel Workflow"
 readme = "README.md"
 requires-python = ">=3.11"

{pyworkflow_engine-0.2.14 → pyworkflow_engine-0.2.15}/pyworkflow/__init__.py

@@ -29,7 +29,7 @@ Quick Start:
     >>> run_id = await start(my_workflow, "Alice")
 """
 
-__version__ = "0.2.14"
+__version__ = "0.2.15"
 
 # Configuration
 from pyworkflow.config import (

{pyworkflow_engine-0.2.14 → pyworkflow_engine-0.2.15}/pyworkflow/celery/tasks.py

@@ -580,6 +580,15 @@ async def _record_step_completion_and_resume(
     )
     await storage.record_event(completion_event)
 
+    # Release the resume_workflow_task singleton lock before scheduling the
+    # next resume. The parent resume task that dispatched this step may still
+    # be holding the (run_id,) lock during its final teardown; without this
+    # release the apply_async below sees the lock held and silently drops
+    # the schedule as a duplicate, leaving the workflow stuck in SUSPENDED.
+    resume_workflow_task.release_lock(
+        task_args=[run_id], task_kwargs={"storage_config": storage_config}
+    )
+
     # Schedule workflow resumption
     schedule_workflow_resumption(
         run_id, datetime.now(UTC), storage_config, triggered_by="step_completed"
@@ -769,6 +778,12 @@ async def _record_step_failure_and_resume(
     )
     await storage.record_event(failure_event)
 
+    # Release the resume_workflow_task singleton lock before scheduling the
+    # next resume (see _record_step_completion_and_resume for details on why).
+    resume_workflow_task.release_lock(
+        task_args=[run_id], task_kwargs={"storage_config": storage_config}
+    )
+
     # Schedule workflow resumption
     schedule_workflow_resumption(
         run_id, datetime.now(UTC), storage_config, triggered_by="step_failed"