You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current implementation of the webhook handler sends feedback data to the Slack webhook using a simple fetch request. While this works under normal circumstances, it lacks resilience in the face of temporary issues such as network instability, timeouts, or Slack service outages. If the webhook call fails due to any temporary issue (e.g., network errors, rate-limiting by Slack, server unavailability), the request will fail permanently without retries, resulting in a poor user experience.
Objective: We should implement a retry mechanism that will attempt to resend the feedback data to Slack a certain number of times before giving up. This will help in ensuring that the request doesn't fail immediately due to temporary issues, improving the robustness of the system.
The text was updated successfully, but these errors were encountered:
The current implementation of the webhook handler sends feedback data to the Slack webhook using a simple fetch request. While this works under normal circumstances, it lacks resilience in the face of temporary issues such as network instability, timeouts, or Slack service outages. If the webhook call fails due to any temporary issue (e.g., network errors, rate-limiting by Slack, server unavailability), the request will fail permanently without retries, resulting in a poor user experience.
Objective: We should implement a retry mechanism that will attempt to resend the feedback data to Slack a certain number of times before giving up. This will help in ensuring that the request doesn't fail immediately due to temporary issues, improving the robustness of the system.
The text was updated successfully, but these errors were encountered: