The distributed documentation offers a Journey of a Task entry outlining how a client.submit is serialized, submitted to the scheduler, handled, computed, etc. up until the task is forgotten.

When using dask collections we are typically not directly using client.submit and this journey might look drastically different, especially when using High Level Graphs.

dask/community#190 (comment)

see also dask/dask#7709