How it works Currently

Currently, the history of webhook invocations is stored in the database AO_A0B856_HIST_INVOCATION and is routinely cleared on a daily basis. The reason for this is that if we were to store it indefinitely, it would considerably increase the size of the database. This could have a significant negative impact on performance, due to the large number of webhooks that get triggered daily by changes in the repositories, especially on busy instances.

Request for Improvement

It would be beneficial if Bitbucket could offer an option in its new feature where admins can configure the retention period for historical webhook success and failure details.

For example, admins might choose to retain data for a specific number of days or a defined number of recent events while discarding older records. This way, teams could strike a balance between retaining critical data for debugging and monitoring and managing the impact on the database's size.