Hi,
We have been using the official API since release, and in recent times changed our webhook URL through the Developer console.
However, some subscriptions are still firing to the legacy webhook address that was set at the time of subscription creation. If the setting is global and not at runtime like #260 request, then these existing subscriptions should be migrated over, or at least guidance should be made on unsubscribing/resubscribing if this is expected behaviour.
For your info, this is clear from the following Datadog trace IDs:
"17081539623400830743" - old URL
"2103169671672759748" - new URL
Thanks,
Dan
Hi,
We have been using the official API since release, and in recent times changed our webhook URL through the Developer console.
However, some subscriptions are still firing to the legacy webhook address that was set at the time of subscription creation. If the setting is global and not at runtime like #260 request, then these existing subscriptions should be migrated over, or at least guidance should be made on unsubscribing/resubscribing if this is expected behaviour.
For your info, this is clear from the following Datadog trace IDs:
"17081539623400830743" - old URL
"2103169671672759748" - new URL
Thanks,
Dan