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

fix: webhook ui failure handling #374

Merged
merged 1 commit into from
Jan 22, 2025
Merged

fix: webhook ui failure handling #374

merged 1 commit into from
Jan 22, 2025

Conversation

mahatoankitkumar
Copy link
Collaborator

Problem

Webhook failures in frontend not handled properly

Solution

added a condition to ignore the 512 status code

@mahatoankitkumar mahatoankitkumar requested a review from a team as a code owner January 21, 2025 13:32
@@ -429,7 +429,7 @@ where
enqueue_alert(error_msg.clone(), AlertType::Error, 5000);
return Err(error_msg);
}
if status.is_server_error() {
if status.is_server_error() && status != 512 {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we ignoring this very specific error code?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a custom error code sent by the webhook.
When the webhook fails, the steps involving the experiment and CAC are already completed. Users receive a false signal that the experiment wasn't created, prompting them to attempt creation multiple times, potentially leading to duplicate experiments.

@ayushjain17
Copy link
Collaborator

why is this pointed to main ?
can we point to saas instead

@mahatoankitkumar
Copy link
Collaborator Author

why is this pointed to main ? can we point to saas instead

saas might take a while to go to prod

Copy link
Collaborator

@Datron Datron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We shouldn't ignore the webhook failure going forward. Rather this should be displayed in the experiments screen otherwise the user assumes even the webhook trigger succeeded.

@Datron Datron merged commit 7f1b273 into main Jan 22, 2025
4 checks passed
@Datron Datron deleted the fix/webhook-ui-handle branch January 22, 2025 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants