Skip to content

Commit 9299ff0

Browse files
authored
Update articles/service-bus-messaging/service-bus-throttling.md
1 parent 6754575 commit 9299ff0

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/service-bus-messaging/service-bus-throttling.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,8 @@ When a request is throttled, it implies that the service is busy because it's fa
8686

8787
As throttling is the expected behavior of any cloud native service, retry logic is built into the Service Bus SDK itself. The default is set to auto retry with an exponential back-off to ensure that we don't have the same request being throttled each time. The default retry logic will apply to every operation.
8888

89-
Note that message-processing code that calls other third-party services may be throttled by those other services as well. For more information on how to handle these scenarios, see the [documentation on the Throttling Pattern](/azure/architecture/patterns/throttling).
89+
>[!NOTE]
90+
> Message-processing code that calls other third-party services may be throttled by those other services as well. For more information on how to handle these scenarios, see the [documentation on the Throttling Pattern](/azure/architecture/patterns/throttling).
9091
9192
### Does throttling result in data loss?
9293

0 commit comments

Comments
 (0)