From 8ea537cc88bcb6c08dc1fae1b988518188535a6e Mon Sep 17 00:00:00 2001 From: Engincan VESKE Date: Fri, 13 Feb 2026 13:25:23 +0000 Subject: [PATCH] Update docs/en/framework/infrastructure/correlation-id.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/en/framework/infrastructure/correlation-id.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/framework/infrastructure/correlation-id.md b/docs/en/framework/infrastructure/correlation-id.md index 1787562033..04fe32108f 100644 --- a/docs/en/framework/infrastructure/correlation-id.md +++ b/docs/en/framework/infrastructure/correlation-id.md @@ -138,7 +138,7 @@ No manual configuration is required. ABP's `ClientProxyBase` automatically reads When you publish a [distributed event](../infrastructure/event-bus/distributed/index.md), ABP automatically attaches the current correlation ID to the outgoing event message. When the event is consumed (potentially by a different service), the correlation ID is extracted from the message and set in the consumer's context. -> This works with all supported event bus providers. Including,[RabbitMQ](../infrastructure/event-bus/distributed/rabbitmq.md), [Kafka](../infrastructure/event-bus/distributed/kafka.md), [Azure Service Bus](../infrastructure/event-bus/distributed/azure.md) and [Rebus](../infrastructure/event-bus/distributed/rebus.md). +> This works with all supported event bus providers. Including, [RabbitMQ](../infrastructure/event-bus/distributed/rabbitmq.md), [Kafka](../infrastructure/event-bus/distributed/kafka.md), [Azure Service Bus](../infrastructure/event-bus/distributed/azure.md) and [Rebus](../infrastructure/event-bus/distributed/rebus.md). ``` Service A publishes event (CorrelationId: abc123)