Sorry have not much time. The labels is complex and should be read als capabilities. In you example you have set exact match to true. This will let the lambda try to match all the labels. And since your job is not containing all, no event is put on the queue to scale. Indeed a runner with those labels could run your job. Can you trie it with exact match set to false?

Sorry for my late reply. I can confirm that if you set the flagexactMatch tofalse it will work, because it is not asserting all the labels are present which makes sense. But this is against the definition ofexactMatch andrunner_extra_labels variables:

exactMatch: "If set to true all labels in the workflow job must match the GitHub labels (os, architecture andself-hosted). When false ifany workflow label matches it will trigger the webhook."

runner_extra_labels: "Extra (custom) labels for the runners (GitHub). Separate each label by a comma. Labels checks on the webhook can be enforced by settingmulti_runner_config.matcherConfig.exactMatch. GitHub read-only labels should not be provided."

If you can not useexactMatch to true to make it work withrunner_extra_labels what is the purpose ofrunner_extra_labels? From my perspectiverunner_extra_labels is a way to extendlabelMatchers list but with the same functionality.

@npalm any update on this?

I had no time yet to dig in this PR. Changes to the wya labels are processed are proven to be risky :(

Anyone that has time to review the PR feel free to dig.

Added a comment in the Issue.
Not absolutely sure, but if what I wrote there is correct, then this pull request isn't necessary and should be closed.