Hi, does anyone know why tasks that were executed ...
# ask-the-community
Hi, does anyone know why tasks that were executed as part of a workflow don't show up in the console task execution list? Same goes for workflows that were executed as subworkflows... Is this a bug or a missing feature or am I missing something else?
@Felix Ruess can you provide an example?
Let my try to elaborate: I created a simple workflow with some container tasks (all in one file). When I run the workflow (runs fine) I can see the execution of this workflow in the flyte console. But if I go to the one of the tasks directly, it doesn't show any executions (although they clearly ran as part of the workflow). Sometimes we also launch these tasks directly, then they show up in the task execution. Same for subworkflows...
I can also provide some screenshots if that helps
oh ok, i think i understand. the "recent executions" for a task are not displayed, even though they have executed as part of a previous workflow. this same behavior occurs with subworkflows as well.
so i'm guessing @Jason Porter may be able to elaborate on the front-end portion of this a little more, but i believe the recent executions are only populated by launchplan executions.
yeah, that would explain it
i believe all of the information is there to populate the recent executions at the granularity you're suggesting however the system is currently not optimized for it. we would have to do a little reconnaissance to figure out how difficult it would be to add.
That would be nice! I'm interested in this since I want to know how long specific tasks took over the last X executions... and I was expecting to see that in the recent executions...
cc @Jason Porter - adding all task executions to the UI for recent executions rather than just those started from a launchplan.
@Felix Ruess another option would be to directly query the admin DB
Copy code
flyteadmin=# select created_at, started_at, duration, updated_at from task_executions where project='flytesnacks' and domain='development' and name='hello-world.say_hello';
          created_at           |          started_at           |  duration   |          updated_at
 2023-01-10 16:17:30.883911+00 | 2023-01-10 16:18:38.725563+00 | 20003019445 | 2023-01-10 16:18:58.74241+00
 2023-01-10 16:17:30.911923+00 | 2023-01-10 16:18:38.743901+00 | 20020004138 | 2023-01-10 16:18:58.776041+00
(2 rows)