Regression: Fixed takeInquiry method not displaying error messages on the client #26976
Conversation
This file contains 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
aleksandernsilva
changed the title
Codecov Report
@@ Coverage Diff @@
## develop #26976 +/- ##
===========================================
- Coverage 40.39% 40.18% -0.22%
===========================================
Files 826 826
Lines 18361 18361
Branches 2020 2020
===========================================
- Hits 7417 7378 -39
- Misses 10645 10686 +41
+ Partials 299 297 -2
Flags with carried forward coverage won't be shown. Click here to find out more. |
MartinSchoeler
previously approved these changes
Sep 29, 2022
…ession/livechat-takeInquiry-client-error
MartinSchoeler
approved these changes
Oct 3, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes (including videos or screenshots)
This pull request brings back the toast message "The maximum number of simultaneous chats per agent has been reached." that should be displayed when an agent tries to take more chats than the maximum allowed.
Issue(s)
Steps to test or reproduce
Further comments
OC-267