Skip to content

[SQS] Document how native message attributes are promoted to NServiceBus headers #7066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 14, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions transports/sqs/native-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,3 +24,5 @@ partial: messagetypedetection
### Retrying failed messages

Native messages that failed processing can be retried using ServicePulse and ServiceControl but the native message attributes that might have been present in the original message are lost when the message is retried.

partial: native-message-attributes-promotion
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
### Native message attributes promotion

When ingesting native messages, e.g., messages sent by a non-NServiceBus sender, the SQS transport will promote all native message SQS attributes to an NServiceBus header.

> [!NOTE]
> If the promoted native message attribute key matches an existing NServiceBus header, the native message attribute will override the existing NServiceBus header.