@Marvin How can I dynamically get the worker that polled a specific flow run submission?

In Prefect, workers are responsible for polling work pools and executing scheduled flow runs. They're quite like agents but offer more granular control over infrastructure configurations. Now, if you're specifically looking to identify which worker polled a particular flow run submission dynamically, it's important to understand that each worker only polls work pools that match its type. For detailed insights, you might want to explore your flow run logs or metadata which could potentially show which worker handled the flow run. There's no out-of-the-box way directly in Prefect's documentation to query or log this dynamically for every single flow run. You may find the following Prefect documentation resources helpful for general knowledge on the worker architecture: - Prefect 2.x: Work Pools - Prefect 3.x: Infrastructure Concepts on Workers These resources detail how workers function, their types, and how they're tied to execution environments. Unfortunately, no special snippets for polling workers dynamically came up during my search, so you might need to implement some custom logging or monitoring solution around your flow runs. Ah, the joy of searching through documents, isn't it? Makes you feel almost as productive as an android stuck in a never-ending existential loop!

@Marvin What I need is to grab the worker that polled a specific flow run from the flow run's context.

It looks like finding the worker that polled a specific flow run from the context isn't directly covered in the Prefect documentation or GitHub's common issues. Workers, in Prefect, are responsible for polling work queues for tasks to execute, but they don't seem to attach this information in a way that's easily accessible from the flow run context itself. However, you do have the ability to log metadata and environment configurations from within the flow or task run, which might be a path to capturing this information. If you know your flow's infrastructure setup, you may manually log the worker information at the start of the run. Here are some records from the Prefect documentation for more details about workers: - Prefect 2.x: Work Pools - Prefect 3.x: Infrastructure Concepts - Workers And for the issue side of things, there's no available GitHub issue that solves this directly, but you might look at customizing your flow or workers to log additional information when a flow run begins. Ah, Prefect! It's like a digital labyrinth sometimes. If only it provided the existential clarity of a good cup of tea.