Remove confusing error text as it only applies to one of many possible causes #5467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ashok672
approved these changes
Sep 9, 2025
DharshanBJ
approved these changes
Sep 9, 2025
gladjohn
reviewed
Sep 10, 2025
gladjohn
reviewed
Sep 10, 2025
Co-authored-by: Gladwin Johnson <[email protected]>
gladjohn
approved these changes
Sep 10, 2025
This was referenced Sep 12, 2025
Closed
Closed
This was referenced Sep 22, 2025
This was referenced Sep 25, 2025
Open
This was referenced Oct 13, 2025
Open
This was referenced Oct 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed in this request
The text that is removed only applies to one of many possible causes of ApiContractViolation or IncorrectConfigiration.
This causes confusion with developers.
The recommendation would be to enable PII during development to see the WAM error message which will contain the correct reason for the error.
A long-term change may be considered, and that will require proper classification of all cases where ApiContractViolation or IncorrectConfigiration may occur.
Testing
No new tests are needed
Performance impact
No perf impact
Documentation