An Azure service that provides an event-driven serverless compute platform.
The issue was resolved after I added configuration for FUNCTIONS_WORKER_PROCESS_COUNT in azure function app.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am giving multiple calls to the Azure activity function from a durable function.
The multiple calls are done and appended to a list and later all calls are fetched using yield to context.task_all
I have the below observations:
For resolving, I tried multiple ways but none of them seems to work. Below are a few steps taken.
The host.json contains the below section already in my case
"concurrency": {
"dynamicConcurrencyEnabled": true,
"snapshotPersistenceEnabled": true
}
I added maxConcurrentActivityFunction
"durableTask": {
"maxConcurrentActivityFunctions":4
}
maxConcurrentActivityFunction impacted the concurrency flow on my local environment but again no impact on the test environment.
Please help me identify the reason for this behavior and the steps I can take to make sure my activity function calls run concurrently even for a few calls or a large number of calls.
Thanks in advance!!
An Azure service that provides an event-driven serverless compute platform.
The issue was resolved after I added configuration for FUNCTIONS_WORKER_PROCESS_COUNT in azure function app.