How can I handle a long-running HTTP action in a Logic App?
My Logic App is triggered by Service Bus and calls an HTTP endpoint that starts a Service Fabric job. The backend operation usually takes about 15 minutes, so…
My Logic App is triggered by Service Bus and calls an HTTP endpoint that starts a Service Fabric job. The backend operation usually takes about 15 minutes, so…
I have a Logic App triggered by Service Bus. It calls a backend Service Fabric service through an HTTP action, but the operation takes about 15 minutes. The…
I'm running a KEDA-triggered Container Apps Job from a Service Bus queue, with one execution per message. Each execution runs a GPU-heavy Python worker that writes dozens of…
I'm running a KEDA-triggered Container Apps Job that reads one message at a time from a Service Bus queue. Each execution runs a GPU workload, and the Python…
I'm encountering some bottleneck issues with my architecture involving API Management and a Service Bus. We're developing an event API that handles requests from 2,000 to 3,000 clients,…
I'm experiencing high load on my API Management setup, which is currently on the Basic Tier. We're developing an event API that handles requests from 2,000 to 3,000…