Parse errors in base.yaml actions not surfaced in DAG UI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 337
- Avg merge
- 20h 58m
- Merged PRs (30d)
- 143
Description
When a DAG fails to parse due to an invalid action definition in base.yaml (e.g., schema JSON parse error), the error only appears in the scheduler/coordinator logs:
field 'actions...input_schema': failed to parse schema JSON: json: cannot unmarshal array into Go struct field ...
The DAG appears in the UI with status "Retry attempts exhausted" but the actual parse error is hidden. The run details show no step output — just a generic dispatch failure.
Expected: Parse errors should be surfaced in the DAG run details, step output, or at minimum the DAG status page.
Impact: Debugging action schema issues requires shell access to read scheduler logs — invisible in the UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with an invalid action definition in base.yaml, then compare the error in the scheduler/coordinator logs with the DAG status, run details, and step output in the UI. Done means the underlying parse error is visible in the DAG run details, step output, or at least the DAG status page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100