From 184f47f2a12265e7ec8b55ac4e5299966ce7a0a9 Mon Sep 17 00:00:00 2001 From: Evan Jarrett Date: Sat, 04 Apr 2026 01:34:55 +0000 Subject: [PATCH] spindle: do not abort pipeline on InitWorkflow failure A single workflow failing to initialize would abort the entire pipeline. Instead, mark the failed workflow and continue processing the rest, matching the existing behavior for unknown engines. Signed-off-by: Evan Jarrett --- spindle/server.go | 10 +++++++++- 1 file(s) changed, 9 insertion(s)(+), 1 deletion(s)(-) diff --git a/spindle/server.go b/spindle/server.go --- a/spindle/server.go +++ b/spindle/server.go @@ -361,7 +361,15 @@ } ewf, err := s.engs[w.Engine].InitWorkflow(*w, tpl) if err != nil { - return fmt.Errorf("init workflow: %w", err) + err = s.db.StatusFailed(models.WorkflowId{ + PipelineId: pipelineId, + Name: w.Name, + }, fmt.Sprintf("init workflow: %s", err), -1, s.n) + if err != nil { + return fmt.Errorf("db.StatusFailed: %w", err) + } + + continue } // inject TANGLED_* env vars after InitWorkflow -- tangled.sh