Skip to content

Commit c67eabe

Browse files
Docs review
1 parent 24add04 commit c67eabe

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

nservicebus/pipeline/events.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,18 +2,16 @@
22
title: Pipeline events
33
summary: Subscribe to events raised by the pipeline
44
component: Core
5-
reviewed: 2024-02-09
6-
versions: '[6,)'
5+
reviewed: 2025-11-26
76
related:
87
- nservicebus/recoverability
98
---
109

1110
The pipeline raises the following notification events:
1211

13-
1412
## Receive pipeline completed
1513

16-
Every time a receive pipeline is completed, a `ReceivePipelineCompleted` event will be raised. This event will not occur when message processing fails e.g. inside a handler.
14+
Every time a receive pipeline is completed, a `ReceivePipelineCompleted` event will be raised. This event will not occur when message processing fails, e.g., inside a handler.
1715

1816
Use the following configuration code to subscribe to the event:
1917

@@ -24,4 +22,4 @@ Subscribing from a [feature](/nservicebus/pipeline/features.md) is shown below:
2422
snippet: ReceivePipelineCompletedSubscriptionFromFeature
2523

2624
> [!NOTE]
27-
> A `ReceivePipelineCompleted` event being raised does not guarantee that the message has been removed from the incoming queue. Infrastructure exceptions can still cause the message to be rolled back and reprocessed.
25+
> A `ReceivePipelineCompleted` event being raised does not guarantee that the message has been removed from the incoming queue. Infrastructure exceptions can still cause the message to be rolled back and reprocessed.

0 commit comments

Comments
 (0)