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

[SNS Logger][Blocked Waiting for Verification] Fix failed escalation count mismatch. #1307

Closed
ear-dev opened this issue Sep 23, 2022 · 2 comments

Comments

@ear-dev
Copy link

ear-dev commented Sep 23, 2022

I can see in our alert room that we had 5 failed escalations on 9/22, however our event logging is only showing 3. Seems like we must have missed some flavors.

In the alert room we got:
2x: {"errorMessage":"Error getting Liveagent response.","error":
1x: {"errorMessage":"Error sending Liveagent chat request.","error":
1x: {"error":"","errorMessage":"Unable to reach Liveagent bot, it may be offline or disabled.",
1x: Status Code: 500 Response: {"error":"Error occurred while using Dialogflow Rest API.

It is unclear to me right now which 3 were properly caught by events. I can investigate.

@ear-dev ear-dev created this issue from a note in Chatbot Client Replacement (Chatbot TODO) Sep 23, 2022
@AlexanderKanakis AlexanderKanakis moved this from Chatbot TODO to In progress in Chatbot Client Replacement Sep 23, 2022
@ear-dev ear-dev changed the title [SNS Logger] Fix failed escalation count mismatch. [SNS Logger][Blocked Waiting for Verification] Fix failed escalation count mismatch. Sep 27, 2022
@ear-dev
Copy link
Author

ear-dev commented Sep 27, 2022

NOTE: It is possible that @AlexanderKanakis 's close chat/event PRs will cover many if not most of these cases. We will wait until we deploy that to verify if we still have a mismatch.

relevant PRs here: https://github.com/WideChat/Apps.Salesforce.LiveAgent/pull/75/files

@ear-dev ear-dev moved this from In progress to Chatbot TODO in Chatbot Client Replacement Sep 27, 2022
@ear-dev ear-dev moved this from Chatbot TODO to Chatbot To Be Groomed in Chatbot Client Replacement Oct 6, 2022
@ear-dev
Copy link
Author

ear-dev commented Nov 1, 2022

It looks like we have just one failed escalation event left to catch, and it is tracked here: #1333

I'm going to close this story for now.

@ear-dev ear-dev closed this as completed Nov 1, 2022
@ear-dev ear-dev removed this from Chatbot To Be Groomed in Chatbot Client Replacement Nov 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants