Skip to content

fix(onboarding): wizard's first run never ran and never saved#287

Closed
gizmax wants to merge 1 commit into
mainfrom
fix/wizard-first-run
Closed

fix(onboarding): wizard's first run never ran and never saved#287
gizmax wants to merge 1 commit into
mainfrom
fix/wizard-first-run

Conversation

@gizmax

@gizmax gizmax commented Jul 22, 2026

Copy link
Copy Markdown
Owner

Finding #29 from first-run testing: 'inputs' vs 'input' (silently dropped -> required-field validation failure), inline run never saved the workflow, and the 202 queued response was presented as an instant success. Wizard now saves the workflow, runs with correct input, and polls to a terminal state. 23 wizard tests + full dashboard suite green.

Three defects in StepRun:
- the API's input field is 'input'; the wizard sent 'inputs', which was
  silently dropped - the run started with no input data and failed
  required-field validation, so the user's first workflow 'did not start'
- the template YAML ran inline and was never saved, so the first workflow
  also never appeared on the Workflows page; it is now saved via
  POST /workflows before running (best-effort - an existing name is fine)
- /workflows/run returns 202 queued; the wizard pretended the queued run
  had already completed. It now polls the run to a terminal state (3s
  interval, 180s budget) and shows the real output or error.
@gizmax

gizmax commented Jul 22, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #288 (contains this fix).

@gizmax gizmax closed this Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant