Is your feature request related to a problem?
Currently, the webhook operates on a fire-and-forget basis, assuming a 200 status without storing the status in the database. This lack of tracking can lead to issues if errors occur.
Describe the solution you'd like
Implement a retry mechanism for non-2XX status codes. This will improve logging and debuggability.
Original issue
Describe the current behavior
Currently webhook is fire and forget. We assume 200 and does not store the status in DB
Describe the enhancement you'd like
Retry mechanism for non 2XX status.
Why is this enhancement needed?
Better logging and debuggability.
Is your feature request related to a problem?
Currently, the webhook operates on a fire-and-forget basis, assuming a 200 status without storing the status in the database. This lack of tracking can lead to issues if errors occur.
Describe the solution you'd like
Implement a retry mechanism for non-2XX status codes. This will improve logging and debuggability.
Original issue
Describe the current behavior
Currently webhook is fire and forget. We assume 200 and does not store the status in DB
Describe the enhancement you'd like
Retry mechanism for non 2XX status.
Why is this enhancement needed?
Better logging and debuggability.