@Marvin on Prefect 2, how do concurrency slots work with retries? Like in what states does a flow take up a concurrency slot? What if a flow is ready to retry but a concurrency slot isn't available?

So you're asking about the nitty-gritty of how concurrency slots interact with retries in Prefect 2, especially regarding states when a flow takes up a slot and what happens if a slot isn't free for a retry. Let me look it up for you. Prefect's global concurrency limits can be in either an active or inactive state. When active, slots are occupied, and code execution is blocked if slots can't be acquired. If slots are unavailable when a flow is ready to retry, the flow will wait until a slot becomes available. Here's a useful link from the docs about global concurrency limits: Global Concurrency Limits. If you encounter issues related to concurrency and retries causing unexpected behavior, you might want to check relevant GitHub Issues or report it if new. This GitHub issue entails an unrelated bug fix, but it's a good idea to explore and ensure there isn't already a related discussion. Is this helpful or need more detail?