Messages not picked up by queue after KEDA scaling in AKS - azure

Question

I have deployed an AKS cluster which I also installed KEDA on. Now this KEDA scaler will schedule a pod for me when a new message appears in an Azure Storage Queue. Each message is processed by one pod, and each pod (except for system pods) will be scheduled on a new node due to it being very resource expensive.
The application on the pod is essentially just an Azure Function written in Node. I found it easier to use it this way because now I don't have to use any SDK's and can just use bindings.
Now KEDA successfully launches one scaled job per message, but when the pod(s) start running I do see the logs of the Azure Functions Runtime saying that it started, but not that it's being triggered by the message in the queue. If I check the queue I also don't see the messages being picked up, they're still there.
Now I also checked the storage connection string environment variable and that's correct.
I found two places where I can make configurations which help me with this: the host.json in the Azure Function and the deployment.yml which I applied for the ScaledJob.
In the host.json I've set the batchSize to 1, batchTreshold to 0.
Below is my yaml to apply. Please don't mind the indentation, it's correct in the file as it's applying fine.
apiVersion: keda.sh/v1alpha1
kind: ScaledJob
metadata:
name: places-job
namespace: places
spec:
jobTargetRef:
parallelism: 10
completions: 1
backoffLimit: 3
template:
metadata:
namespace: places
labels:
app: places
spec:
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: app
operator: In
values:
- places
topologyKey: kubernetes.io/hostname
containers:
- name: places
image: {azure-container-registry}:latest
env:
- name: AzureFunctionsJobHost__functions__0
value: places
envFrom:
- secretRef:
name: places
readinessProbe:
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 240
httpGet:
path: /
port: 80
scheme: HTTP
startupProbe:
failureThreshold: 3
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 240
httpGet:
path: /
port: 80
scheme: HTTP
resources:
limits:
cpu: 4
memory: 10G
restartPolicy: Never
pollingInterval: 10 # Optional. Default: 30 seconds
successfulJobsHistoryLimit: 1 # Optional. Default: 100. How many completed jobs should be kept.
failedJobsHistoryLimit: 1 # Optional. Default: 100. How many failed jobs should be kept.
triggers:
- type: azure-queue
metadata:
queueName: places-requests
queueLength: "1"
activationQueueLength: "0"
connectionFromEnv: AzureWebJobsStorage
accountName: {storage-account-name}
Does anyone know any other setting I might have to tweak so that the newly deployed pods/nodes do pick up the messages from the queue?