The issue has been resolved. It was occurring in published versions due to the updater having the wrong version. We manually did this process to transition the webhook to its normal piece.
However, there was an issue during the migration. It has been fixed now.
Upon retrospectively examining this section of code, I also found the fallback was in place where the payload was stored failed because the issue occurred before, resulting in the payload not being saved and thus unable to be replayed later.
We appreciate your trust in us and are committed to improve our monitoring to address this blind spot. We apologize for any inconvenience caused.
Regards,
Mo