Currently, when a custom webhook (e.g., sending appointment data to an external endpoint like Power Automate) fails due to issues on the receiving end, Chili Piper dont logs the failure and does not provide an option for admins to manually resend the specific failed event(s) from the Meetings Activity or Events History dashboard. Support has confirmed there is no built-in mechanism to re-trigger these failed webhook payloads, which creates operational challenges, such as manual recreation of appointments or reliance on API workarounds. This is particularly impactful for high-volume users where failures (e.g., due to endpoint timeouts) can lead to missed bookings and lost revenue.

Proposed Solution:
Introduce a manual resend/replay option for failed custom webhook events directly within the Chili Piper Admin Dashboard (e.g., under Meetings Activity or a dedicated Webhook Logs section). The feature should:

1. Display detailed logs of failed webhook attempts, including timestamps, payload details, and error messages (e.g., HTTP 500, timeout).
2. Allow admins to select individual or bulk failed events and trigger a one-click resend to the original endpoint.
3. Support idempotency to prevent duplicate processing (e.g., by including unique event IDs in payloads).
4. Provide an option to edit the payload or endpoint URL before resending (e.g., to fix a misconfigured Power Automate URL).
5. Notify admins of resend outcomes (success or failure) via email or in-app alerts.