@Marvin I'm utilizing a global concurrency limit to prevent race conditions by setting the concurrency slot to 5. There are

with

contexts waiting for an extended period to acquire a slot. However, even when a slot becomes available, the long-waiting

with

context manager does not start.

The global concurrency limits in Prefect are designed to manage execution efficiently, but if your

with

contexts are waiting for an extended period and not starting even when slots become available, it might be related to the configuration of the concurrency limits. The documentation mentions a

slot_decay_per_second

parameter that can be set to control how quickly slots become available. Setting a higher value for this parameter would result in slots becoming available more quickly. If you are experiencing issues with concurrency slots, you might want to review the

slot_decay_per_second

setting and adjust it according to your needs. For more detailed information, refer to the Prefect documentation on global concurrency limits: Global Concurrency Limits If adjusting the settings does not resolve the issue, you may consider searching for related GitHub issues or seeking further help from the Prefect community.

@Marvin I already checked

active slots

were 0.

It seems there might be a specific issue regarding global concurrency limits and

with

contexts that wait for an available slot. A pull request in the Prefect GitHub repository that could be relevant to your issue has been found, which closes an issue related to this matter. You can check out the pull request and the related discussion for more insights into the problem: Documentation for global concurrency limits PR This pull request closes issue #10495, which might contain additional information on your problem. If this does not help, you might want to create a new issue in the Prefect GitHub repository to get a direct response from the maintainers.