Fix NotMapped exception when clearing task instances with downstream/upstream #58922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When clearing task instances with include_downstream or include_upstream enabled,
the clear operation would fail with a NotMapped exception if any task was specified
with a map_index tuple but wasn't actually a mapped task. This happened because the
code assumed all tasks specified as tuples were mapped tasks and called
get_mapped_ti_count() on them without handling the NotMapped exception.
The fix catches the NotMapped exception and treats such tasks as normal tasks instead.
related to: #57758
Error seen in api-server when I try to clear task instances