Skip to content

Async Retrospective: Automated Disabling of Failed Webhooks Release

Background

In %15.7, we released the feature "Automated disabling of failing webhooks".

This is an async retrospective to consider the process of delivering this feature and what we've learned in the process. We do regular async retros each milestone, but this will be a focused retro on delivery of this particular feature over the the course of multiple milestones.

We'll keep this issue public from the beginning so customers/users are welcome to weigh in with productive and blameless feedback as well.

Following the release of this feature we identified two significant issues:

  • the feature applied to group hooks as well, which were getting disabled without calls-to-action or notifications for them to be re-enabled: #385902 (closed)
  • the SQL query used to fetch web-hooks excluded hooks with expired suspensions: #387938 (closed)

The primary concern of this retrospective should be to explore these two significant regressions and bugs, to try and establish root-causes.

However, please feel free to create new threads to explore any gaps/challenges that arose related to this release or through development of this release.

Process

Consider the process of delivering this feature and ask yourself:

🌟 what praise do you have for the group?

👍 what went well for the development and release of this feature?

👎 what didn’t go well the development and release of this feature?

📈 what can we improve going forward?

Honestly describe your thoughts and feelings below.

We'll close the issue on Feb 17.

Edited by Grant Hickman