An Azure service that automates the access and use of data across clouds without writing code.
Hello @José Gomes
Your evidence is consistent with an ambiguous send outcome: Service Bus accepts the operation, but the acknowledgment doesn’t return to the caller before the managed connector times out. Microsoft documents this exact failure class when a message is committed but the acknowledgment is lost; retrying can create duplicates.
However, the available metrics aren’t sufficient to confirm a West Europe platform incident or identify where the 120 seconds were spent. That requires Microsoft’s managed-connector backend telemetry. Check Azure Service Health > Health history for the affected subscription and UTC periods. Resolved service issues remain visible there for 90 days. If nothing appears, open an Azure support request and provide:
- Logic App names, workflow run IDs, and correlation IDs
- API connection resource IDs
- Service Bus namespace and entity names
- Exact UTC timestamps for successful and timed-out operations
- Action inputs/outputs, retry history and tracking identifiers
- Message IDs and lock tokens for representative examples
Logic Apps exposes the workflow correlation ID and action retry information in run history, which Microsoft Support can correlate with backend traces.
Managed identity is a supported authentication method for the Service Bus managed connector. The simultaneous impact across independently created connections makes an isolated RBAC or expired-credential problem less likely, but it doesn’t prove a regional connector incident.
For recurrence mitigation:
- Enable Service Bus duplicate detection and supply a stable MessageId based on the business operation. Standard tier supports duplicate detection. When the same MessageId is sent again within the configured detection window, Service Bus accepts the request but discards the duplicate. The managed connector’s Send message action exposes the MessageId property.
- Review the Send message retry policy. Setting it to none can prevent automatic action retries, but it also removes recovery from genuine transient failures and still leaves the original send outcome unknown. Duplicate detection plus a stable ID is therefore safer than relying solely on disabled retries. Logic Apps supports default, none, fixed, and exponential policies when the operation exposes retry settings.
- Make downstream processing idempotent. Duplicate detection protects repeated sends only within its configured window; consumers should still reject an already-processed business-operation ID.
- Treat the completion failures separately. Under peek-lock, an expired or unsettled lock increases DeliveryCount. Once MaxDeliveryCount is exceeded, Service Bus moves the message to the dead-letter queue with MaxDeliveryCountExceeded. Increasing that value may provide temporary operational headroom, but it doesn’t correct the failed settlement path.
- For the most critical workflows, evaluate Logic Apps Standard with the built-in Service Bus connector. Consumption supports only the shared managed connector, while Standard also provides the built-in connector, which Microsoft documents as generally offering better performance and configurable send/receive timeouts.
The documented timeout controls apply to the Standard built-in connector, so they shouldn’t be presented as a Consumption workaround.
References:
- Connect to Azure Service Bus from Azure Logic Apps
- Service Bus managed connector reference
- Duplicate detection in Azure Service Bus
- Logic Apps error handling and retry policies
- Service Bus message transfers, locks and settlement
- Service Bus dead-letter queues
- View Azure Service Health issues
Help make this community better for everyone: If this answer helped or resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution. Thank you.