Global Webhooks do not report all possible SDK payload changes

TL;DR

Upgrade to a build containing both, then verify delete events on your version, since the reporter noted SDK deletion still did not trigger right after #2592. Source: https://github.com/growthbook/growthbook/issues/2525 (GrowthBook)

Steps

1. If GrowthBook global webhooks miss SDK payload changes (toggling encryption, creating or deleting SDK connections), this was fixed in two passes: PR #2533 for the general payload-change coverage and PR #2592 for SDK connection create and delete events. Upgrade to a build containing both, then verify delete events on your version, since the reporter noted SDK deletion still did not trigger right after #2592.
2. Source: https://github.com/growthbook/growthbook/issues/2525 (GrowthBook)

When to use

Use this skill when you run into "Global Webhooks do not report all possible SDK payload changes".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/growthbook/growthbook/issues/2525

In gh:growthbook/growthbook#2525, the issue was: ### Summary

The Global Playbooks documentation states that the webhook is triggered when the SDK payload changes, but there are some cases where this is not the case, like when the user changes the SDK to be encrypted. Creations and deletions are also not notified.

Expected Behavior

All operations that change, create, or delete SDKs in any way should be notified

Current Behavior

Only a subset of operations like feature flag changes are notified.. The verified answer: If GrowthBook global webhooks miss SDK payload changes (toggling encryption, creating or deleting SDK connections), this was fixed in two passes: PR #2533 for the general payload-change coverage and PR #2592 for SDK connection create and delete events. Upgrade to a build containing both, then verify delete events on your version, since the reporter noted SDK deletion still did not trigger right after #2592.. Issue URL: https://github.com/growthbook/growthbook/issues/2525