Skip to content
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

Better logging for when saga data is not found for an incoming message #6252

Merged
merged 1 commit into from
Feb 4, 2022

Conversation

TravisNickels
Copy link
Member

@TravisNickels TravisNickels commented Feb 3, 2022

Previously, when saga data cannot be found for an incoming message, this would be logged as:

Could not find a started saga for '{MessageType}' message type. Going to invoke SagaNotFoundHandlers.

This has been updated slightly, to:

Could not find any started sagas for message type '{MessageType}'. Going to invoke SagaNotFoundHandlers.

And for each saga that handles the message (in case there are multiple) an additional item is logged:

Could not find a started saga of '{SagaType}' for message type '{MessageType}'.

@TravisNickels TravisNickels self-assigned this Feb 3, 2022
@DavidBoike DavidBoike added this to the 7.7.0 milestone Feb 3, 2022
@DavidBoike DavidBoike marked this pull request as ready for review February 4, 2022 20:59
@TravisNickels TravisNickels merged commit 7fb48b0 into release-7.7 Feb 4, 2022
@TravisNickels TravisNickels deleted the 7.7-saga-type-info branch February 4, 2022 21:35
@DavidBoike DavidBoike changed the title 7.7 saga type info Better logging for when saga data is not found for an incoming message Mar 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants