fusion/.changeset/workflow-capacity-scheduler.md at ae63cd9008ffc5bfdc57407bf677b24fc818e861

Files

gsxdsm 4b4c32dc18 FN-6063: enforce workflow scheduling capacity after hold release

Keep scheduler capacity checks aligned with fresh task state during workflow dispatch.

- bypass the startup slim-list memo when scheduling and after workflow hold release sweeps
- clear the startup slim-list memo when task.json writes move tasks between columns
- treat capacity-exhausted moveTask rejections as queued dispatches, log the reason, and cover the behavior with scheduler/store tests
- add a patch changeset for the published CLI package

Files changed:
 .changeset/workflow-capacity-scheduler.md          |  5 +++
 packages/core/src/__tests__/store-movement.test.ts | 15 ++++++++
 packages/core/src/store.ts                         |  1 +
 packages/engine/src/__tests__/scheduler.test.ts    | 40 ++++++++++++++++++++--
 packages/engine/src/scheduler.ts                   | 25 ++++++++++----
 5 files changed, 77 insertions(+), 9 deletions(-)

Fusion-Task-Id: FN-6063

Fusion-Task-Lineage: 80ddc0e7-f78d-483c-886a-27c4c07bde7a

2026-06-09 02:03:22 -07:00

163 B

Raw Blame History

@runfusion/fusion

@runfusion/fusion
patch

Fix workflow scheduling so in-progress column limits are enforced from fresh task state after hold-advancing sweep dispatches.

163 B Raw Blame History

163 B

Raw Blame History