[AVM Module Issue]: KEDA scaler not scaling from zero

[wortner]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

I'm not sure

(Optional) Module Version

latest

(Optional) Correlation Id

No response

Description

Everything deploys fine. I can manually run the job. But the scaler is not scaling up from zero. I don't know how to debug. This is all I have from logs.

2025-06-11T08:18:55.67015656Z
Scaler github-runner is built.
2025-06-11T08:18:55.63391482Z
Scaler github-runner is built.
2025-06-11T08:18:21.376718906Z
Scaler github-runner is built.
2025-06-11T08:18:21.363384211Z
Scaler github-runner is built.
2025-06-11T07:03:17.318102548Z
Scaler github-runner is built.
2025-06-11T07:03:17.300311732Z
Scaler github-runner is built.
2025-06-11T06:56:24.175766646Z
Scaler github-runner is built.
2025-06-11T06:56:24.163541254Z
Scaler github-runner is built.
2025-06-11T06:29:58.262615339Z
Scaler github-runner is built.
2025-06-11T06:29:58.245376718Z
Scaler github-runner is built.
2025-06-10T14:35:25.605515269Z
ScaledJob is ready for scaling
2025-06-10T14:35:25.599480119Z
KEDA is starting a watch for revision '' to monitor scale operations for this revision
2025-06-10T14:35:25.593907171Z
Scaler github-runner is built.
2025-06-10T14:33:59.375288891Z
ScaledJob was deleted
2025-06-10T14:33:59.32893572Z
KEDA is stopping the watch for revision '' to monitor scale operations for this revision

[wortner]

When I change min excutions from 0 to 3 it creates probably 3 instaces of the job which are consuming the Github workflows just fine. But I want scaling to zero. So the problem is with scaler.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[jaredfholgate]

Hi. Thanks for reporting this. We'll need to attempt a reproduction as it is not something we've seen before. Not sure when we'll have time to test, but hopefully going to leverage this module in the ALZ IaC Accelerator soon, which will provide better testing of the scale out.