Hartmut/HartOMat
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: add graph workflow fallback and retry metadata

Browse Source
This commit is contained in:
Hartmut Nörenberg
2026-04-07 10:56:45 +02:00
parent c17b7d2e8f
commit f9d4da52b9
9 changed files with 473 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/workflows/WORKFLOW_DELIVERY_CHECKLIST.md
+2 -2
View File
@@ -28,9 +28,9 @@
- [x] Workflow context introduced
- [x] Node outputs are persisted and reusable
- [ ] Graph runtime supports legacy fallback
- [x] Graph runtime supports legacy fallback
- [ ] `legacy`, `graph`, and `shadow` modes exist
- Progress: Graph dispatch now executes the extracted bridge nodes (`order_line_setup`, `resolve_template`, `material_map_resolve`, `auto_populate_materials`, `glb_bbox`) synchronously, persists per-node outputs/logs/durations onto `WorkflowNodeResult`, and continues to queue render/export nodes through Celery without changing the legacy preset dispatcher.
- Progress: Graph dispatch now persists retry/failure policy metadata per node, retries bridge-node failures within the configured attempt budget, and the production order-line dispatcher can opt into explicit graph mode with a hard fallback back to legacy dispatch if graph execution preparation or runtime fails.
### Phase 5