This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(76.8, 69%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGG%3C/text%3E%3C/svg%3E)
Hi there,
I have been playing around with a container app, I created a revision where the scale is 0-5 with a scale rule of type custom (**azure-servicebus)
**
I created a secret within the container app for the service bus connection string.
I then added a authentication reference with the secret & a trigger of "connection"
The meta data is following the keda documentation:
activationMessageCount: 1
connectionFromEnv: secretName
nameSpace: ServiceBusNameSpace
queueName: ServiceBusQueueName
But when creating the revision, it always states it is running. I would think with the min scale set to 0 it would be not running until the trigger is set off from the servicebus queue?
Another issue is that it does not scale at all. When sending 30 messages via the queue the metric sits @ 1 replica count.
Please help! I can not find anyone else having this issue - so I am guessing it is just a setup issue.
Thanks in advance!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(294.40000000000003, 87%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMU%3C/text%3E%3C/svg%3E)
Hello @Gareth Glanville - Sorry for the late reply. Were you able to resolve this issue? I'll try to reproduce and report back with any findings.
I have the same issue and logged it at microsoft/azure-container-apps:
https://github.com/microsoft/azure-container-apps/issues/952
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(195.2, 93%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
I'm curious about your use of Container App vs Container App Jobs. (Genuinely just curious about your use case.)
However, I think your issue may be that you want to use messageCount vs activationMessageCount.
activation is related to scaling only from zero to one.
From the KEDA docs on activation and scaling https://keda.sh/docs/2.14/concepts/scaling-deployments/#activating-and-scaling-thresholds:
IsActive function and only applies to 0<->1 scaling. There are use-cases where the activating value (0-1 and 1-0) is totally different than 0, such as workloads scaled with the Prometheus scaler where the values go from -X to X.
I was facing the same issue, when only one replica was running even though I had multiple messages on the queue. I added messageCount to 1 in metadata of event driven scaling and then it started working. Looks like KEDA although mentiones it as optional, uses somehow to scale the replicas.