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
[VDG] Chat workflow better error handling #12391
[VDG] Chat workflow better error handling #12391
Conversation
Co-authored-by: molnard Co-authored-by: Szpoti Co-authored-by: soosr Co-authored-by: ichthus1604 Co-authored-by: SuperJMN Co-authored-by: lontivero Co-authored-by: adamPetho Co-authored-by: kiminuo
… into features/bab
{ | ||
OnStepError.SafeInvoke(this, ex); | ||
|
||
// TODO: Roland, are we 100% sure we want to swallow errors and not log them? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should store the Exception instead of counting the error. So if the same exception keeps happening then only log it once. Meanwhile if there is a new exception we need to log that too.
Review:
|
What is the point of merging this PR? The same commits by Fede are in the other PR #12181 and they were even reverted there. |
I didn't merge this intentionally, it got automatically merged by git when I merged the other PR |
Changes from this PR are not even visible on master. |
Improves error handling on #12181
This will show the error dialog only the first time an error comes out for a non-interactive step (such as
StartConversationStep
). For interactive steps (which require user input), these are reset whenever an error occurs within their execution, which means the user will have to re-enter their input in order to retry the action, which is the expected UX:Interactive:
user input -> try action -> error message -> user input -> retry action -> error message -> user input....
Non interactive:
try action -> error message -> retry action -> silently fail -> retry action....