How to enforce AutoMaterialize runs to start and enqueue indiviual ops even if there are no concurrency slots available?

[nicoviniegra]

In version 1.9 my automaterialize runs got to In Progress as soon as they were triggered and individual assets got enqueued based on priority even if there were no concurrency slots available.

After upgrading to version 1.11 this behaviour changed and now when there are no concurrency slots available, the automaterialize run gets enqueued instead of starting and enqueuing the individual assets. This makes high-priority assets within the auto_materialize runs to not get enqueued properly in the queue based on their priority until a concurrency slots opens and lets the run to get In Progress. Only then assets get enqueued correctly based on their priority.

How can i restore the behaviour i had in version 1.9? I want the automaterialize runs to get in progress once they are triggered (even when there are no concurrency slots available) and get the individual runs queued so high-priority can start as soon as a concurrency slot opens