Found some inconsistency when using client API to ...
# ask-metaflow
h
Found some inconsistency when using client API to query some task / run metadata compared to UI. Is that a bug or intentional? In particular client API returns
finished: false, finished_at: null
for failed tasks and runs, while the metaflow UI backend returns
status: failed, finished_at: <timestamp>
1