Hello @Chip Felton
This issue you mentioned occurs because the core tools use a single host for all functions, and the host only listens to a single blob trigger per container.
To work around this issue, you can use the host.json
file to configure the host to listen to all blob triggers in the container. You can add the following configuration to the host.json
file:
{
"version": "2.0",
"extensions": {
"blobs": {
"maxDegreeOfParallelism": 1,
"batchSize": 1,
"newBatchThreshold": 0
}
}
}
This configuration sets the maxDegreeOfParallelism
to 1, which means that the host will only process one blob trigger at a time. It also sets the batchSize
and newBatchThreshold
to 1, which means that the host will process each blob trigger as soon as it arrives.
With this configuration, the host will listen to all blob triggers in the container, and all of your blob triggered functions should be triggered when a blob is added or updated in the container.
I hope this helps.