Body
We can handle this programmatically, but currently there’s no user interface available for this. The “Clear” button in the task modal applies to all the mapped tasks no matter which map index is chosen (which also is a UX issue), while the clearTaskInstances API only takes a list of task IDs.
Currently DAG.clear() supports passing in a 2-tuple instead of string to clear one single mapped task (e.g. task_ids=[("my_task", 1)]). But I’m not sure how to expose this in the REST API—something like {"task_ids": [["my_task", 1], "another_task"]} is difficult to spec in Open API.
Committer
Body
We can handle this programmatically, but currently there’s no user interface available for this. The “Clear” button in the task modal applies to all the mapped tasks no matter which map index is chosen (which also is a UX issue), while the
clearTaskInstancesAPI only takes a list of task IDs.Currently
DAG.clear()supports passing in a 2-tuple instead of string to clear one single mapped task (e.g.task_ids=[("my_task", 1)]). But I’m not sure how to expose this in the REST API—something like{"task_ids": [["my_task", 1], "another_task"]}is difficult to spec in Open API.Committer