Skip to content

operationId not set when message is unsolicited#373

Merged
Jonopono123 merged 4 commits into
developfrom
NIAD-387-no-operationId-for-unsolicited-messages
Mar 12, 2026
Merged

operationId not set when message is unsolicited#373
Jonopono123 merged 4 commits into
developfrom
NIAD-387-no-operationId-for-unsolicited-messages

Conversation

@Jonopono123

@Jonopono123 Jonopono123 commented Mar 12, 2026

Copy link
Copy Markdown
Contributor

What

Remove OperationId from header when incoming message is unsolicited

Why

When an incoming message is unsolicited, an operationId is generated but doesn't actually have any correlation to anything in the system.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Internal change (non-breaking change with no effect on the functionality affecting end users)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated the Changelog with details of my change in the UNRELEASED section if this change will affect end users

@Jonopono123 Jonopono123 requested a review from a team as a code owner March 12, 2026 14:46
@Jonopono123 Jonopono123 marked this pull request as draft March 12, 2026 14:46
@github-actions

Copy link
Copy Markdown

Images built and published to ECR using a Build Id of PR-290-a18f4f9

@Jonopono123 Jonopono123 marked this pull request as ready for review March 12, 2026 16:24
@Jonopono123 Jonopono123 merged commit 8ba7663 into develop Mar 12, 2026
7 checks passed
@Jonopono123 Jonopono123 deleted the NIAD-387-no-operationId-for-unsolicited-messages branch March 12, 2026 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants