Add structured log for webhook flagged as failing after all retries exhausted

[Chucks1093]

Summary

When a webhook exhausts all delivery retries and is flagged as failing, an error-level log should be emitted with enough context for an operator to identify the webhook and manually investigate the callback URL.

Scope

• Emit a structured error log when a webhook is flagged failing after retry exhaustion with fields: webhook_id, creator_id, event_type, total_attempts, last_error_code, flagged_at
• Callback URL must not appear in the log — use the masking helper
• Log is emitted once per exhaustion event, not on each failed attempt

Acceptance Criteria

• Error log emitted exactly once on retry exhaustion
• All six fields present with correct values
• Callback URL absent from log output
• Log not emitted on individual retry failures (those use the existing retry log)

ETA: 12 hours

---

Coordinate on Telegram

[GBOYEE]

Hello! I'd love to pick this one up. I can handle this one. I'll implement it to spec and add tests. I can put up a PR for this once claimed.

[Ayinkx]

Hi i would like to work on this issue
please

[DavidAkere204]

I would like to work on this issue

[dubemoyibe-star]

I'd like to work on this.

I'd update the webhook retry flow so an error log is emitted only when a webhook has exhausted all retry attempts and is marked as failing. The log will include the required fields (webhook_id, creator_id, event_type, total_attempts, last_error_code, and flagged_at) while ensuring the callback URL is never exposed by using the existing masking helper.

I'll also add tests to verify the log is emitted exactly once on retry exhaustion, contains the expected metadata, excludes the callback URL, and is not generated for individual retry failures.

Estimated completion: 12 hours.

[Phantomcall]

I'd like to take this on.

I have experience implementing structured logging and observability for backend services, with a focus on producing actionable operational logs while avoiding exposure of sensitive information.

For this issue, I'll:

• Emit a single structured error-level log when a webhook transitions to the failing state after exhausting all retry attempts.

• Include the required fields: webhook_id, creator_id, event_type, total_attempts, last_error_code, and flagged_at.

• Ensure the callback URL is never logged directly by using the existing masking helper.

• Keep the existing retry-attempt logging unchanged so the new error log is emitted only once per retry-exhaustion event.

• Add/update tests verifying:

  • the error log is emitted exactly once,
  • all required fields are present and accurate,
  • the callback URL is absent from the log output,
  • no error log is produced during intermediate retry attempts.

I'll keep the implementation scoped to the retry exhaustion path, preserve existing behavior, and verify the complete test suite passes before submitting the PR.

GitHub: @PHANTOM_CALL

[damzempire]

i would like to work on this issue as a full stack and smart contract developer

[grantfox-oss]

🦊 GrantFox — @dubemoyibe-star has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #587)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@dubemoyibe-star's PR #594 was approved and merged by @Chucks1093.

🏆 @dubemoyibe-star: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,144 total points). Track your full progress on GrantFox.

👏 Great work, @dubemoyibe-star! Keep contributing to accesslayerorg.