When configuring outgoing webhooks (e.g., to GitHub Actions or Slack), errors and failures are not surfaced to the user, making troubleshooting difficult and time-consuming. Currently, after a webhook is triggered (or fails to trigger), there is very limited visibility into what payload was sent, what response was received, or whether an error occurred. If a webhook fails silently or returns an error, I have no way to view detailed logs or the history of webhook attempts. Furthermore, error messages (if any) seem to clear out whenever CI job settings are saved, and there is no persistent record of webhook activity.
This "blind debugging" increases the time and frustration required to resolve issues.

Proposed Solution:

Implement a persistent, searchable log or history for all outgoing webhook events in Gearset CI jobs, including:

Timestamp of every webhook trigger (success or failure)
Payload sent (with sensitive fields masked)
Response code and body from the target endpoint
Detailed error message if the webhook fails to send or receives an error
Ability to manually re-trigger a webhook for testing
Optionally, retain recent webhook logs even after CI job settings are updated

This would empower users to quickly debug integration issues, validate payloads, and confirm that notifications and actions are working as intended. Having a clear audit trail of webhook activity