galaxyproject / galaxyproject/galaxy
Invoking a workflow with missing RuntimeValues should fail to schedule
Open
area/API
area/workflows
kind/bug
kind/enhancement
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 169
Description
I think this would avoid problems such as #4399, which are pretty hard to diagnose. If a runtime parameter hasn't been specified we should abort early and return with a meaningful error message.
Running a workflow halfway to have it abort is not great UX.
It should also be more apparent which parameters are runtime parameters in the workflow editor ... finding them is hard if you have a large workflow.
Contributor guide
Assessment
This issue has not been assessed yet.