What are the reasons that a task would finish with a "finished task run for task with final state: 'Pending'"? My pipeline runs and all tasks succeed up until one of the tasks return with a "Pending" status. Then after this, the system says: "Flow run RUNNING: terminal tasks are incomplete" and then "Beginning Flow run for ...." but then nothing else is printed and it looks like its just hanging there. I have let the system sit there for a long while but it really seems like its hanging and not waiting for the Pending tasks. Any ideas?

Hmm, I haven't seen a task run ending in a Pending state before - just awaiting execution. Following this list of state transitions, this Pending state should resolve into a Scheduled or Running state (or eventual subclass Failure) based on your task configurations, but it's not even making it there. I wonder if there is some task run logic that needs to be resolved to move this task run to a Running state.

The log is very long but here you go:

Very strange - the task ends in a 'Pending' state almost immediately. I'm going to do some more digging but this may be best resolved as a Github issue, for visibility with the development team.

Cool I can open one in a bit. With all the details. The flow is entirely runnable by the public too so the dev team can try that as well if they so choose

Awesome, thank you for the context. It does look like this may be a result of the mapping with

get_minutes_item_file_details

as you mentioned, which recently underwent a refactor to accommodate DFE - especially considering you are using the

DaskExecutor

.

For tracking: https://github.com/PrefectHQ/prefect/issues/2841