When production data is copied to a sandbox, webhooks are copied with the same Enabled/Disabled status as production. This can result in enabled sandbox webhooks continuing to point to production endpoints and potentially triggering external production systems from sandbox activity. This behavior appears inconsistent with other configurations, such as Jira Automation, which are handled more cautiously during the copy process

What is Needed:
During a Copy production data operation, all copied webhooks should be disabled by default in the sandbox to prevent unintended requests to production or other external systems.

Alternatively, the copy process should provide administrators with an option to choose whether copied webhooks should be disabled, or display a clear warning/confirmation informing them that enabled webhooks will be copied in their current state and may trigger their configured endpoints.

The goal is to provide a safer and more consistent sandbox refresh experience while still allowing customers to intentionally enable webhooks when required for testing