fix: update progress callback and event types for workflow execution
Deploy Development / deploy (push) Successful in 56s
Build Test / pytest-backend (push) Successful in 4s
Build Test / lint-backend (push) Successful in 0s
Build Test / build-frontend (push) Successful in 16s

- Changed progress callback from "execution_complete" to "workflow_graph_finished" to provide intermediate updates.
- Updated documentation to clarify the distinction between "workflow_graph_finished" and "execution_complete".
- Adjusted frontend API handling to accommodate new event structure and ensure proper result serialization.
This commit is contained in:
Lars committed 2026-04-18 09:11:07 +02:00
1 parent a002781ef9
commit 0ad3ddd627
3 files changed
+30 -14

No files matched your search

+4 -2
View File
@@ -213,9 +213,11 @@ async def execute_workflow(
logger.info(f"Workflow execution completed: {execution_id}")
# NEW: Progress-Callback für erfolgreiche Fertigstellung
# Fortschritt: kein type=execution_complete — das sendet /execute-stream einmalig
# mit vollem execute_prompt_with_data-Result (Pipeline/Base/Workflow), sonst schließt
# der Client nach Workflow vorzeitig ohne debug/node_states oder Pipeline bricht ab.
if progress_callback:
await progress_callback("execution_complete", {
await progress_callback("workflow_graph_finished", {
"execution_id": execution_id,
"status": "completed",
"aggregated_result": aggregated,