North Central resource service bus timeout exceptions, started with no changes made

Hello Vlad Tkachenko,

Thanks for reaching out on Microsoft Q&A and really appreciate your patience while we looked into this.

From your description, we are sorry to hear you're running into an issue where your Azure pipeline is stuck while trying to provision a Logic App.

Few things you can check:

1. Connectivity Issues / Firewall / Network Path From the Service Bus Troubleshooting Guide: timeouts occur when the client cannot reach the service due to network/firewall settings, wrong DNS, or blocked ports.
2. Service Maintenance: Timeouts are often expected during maintenance operations like Service Bus updates or OS updates. You can check the Azure Service Status page to see if there are any ongoing issues in your region.
3. Default Connection Limit: The DefaultConnectionLimit property can also cause timeouts if it's reached. Make sure to review this in your application to see if it needs adjustment.
4. Monitor for Load: High load conditions either on the client side (like high CPU usage) or in the service could also result in timeouts. Check to see if there is any performance degradation at the times you're seeing the timeouts.
5. SDK Client Timeout and Retry Policies The client library has default operation timeouts; if operation takes longer (due to load, queue depth, latency), then a TimeoutException may occur. The client may retry, but if all retries fail it surfaces the exception.
6. Service Bus Resource Health / Regional Outages Azure resources may have temporary service degradation in specific regions. Service Health / Metrics can show this. Microsoft docs suggest verifying Service Bus namespace Resource Health.
7. SDK version bugs Sometimes older versions of the SDK have bugs that manifest as start-from-cache or duplex link timeouts. Updating SDK may help.

If none of these resolutions seem to be addressing your issue, let’s gather a bit more information:

• Are you experiencing this issue consistently, or is it intermittent?
  • Have there been any changes to your environment or configurations recently before this issue started?
  • Can you provide any additional context, like the type of application you are using (e.g., .NET, Java, etc.) and the specific operations being performed when the timeout occurs?
  • Whether metrics or monitoring show performance degradation, or logs with more detailed stack traces. https://azure.status.microsoft/en-us/status
    https://docs.azure.cn/en-us/service-bus-messaging/service-bus-troubleshooting-guide I hope the provided answer is helpful, do let me know if you have any further questions on this
    Thanks