[hamzahalq]

Adds Suggest with AI beside a subscription's retry policy. It looks at the subscription's recent failures, proposes a policy, and shows what each kind of failure would do under the current and the suggested policy. Nothing is saved until the user saves it as a new policy.

• Sent to the provider: each kind of failure as one masked first line (values, quotes, emails and URLs taken out) with counts and how often a retry fixed it, plus the current policy's rules without alert settings. No documents or response bodies.
• The answer is checked like a saved policy; alerts are never taken from it.
• Recorded in the audit log as suggest-retry-policy before sending. Needs subscriptions.view and retry-policies.create.
• Uses the (SubscriptionId, FinishedOn) and RetryFor indexes; tested at 1.4M rows.
• Only failures since 2026-10-14 carry a subscription id, so older ones aren't seen.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 8

• ^main$
• ^master$
• ^staging$
• ^development$
• ^gigstaging$
• ^develop$
• ^releases$
• ^releases/r10.0$

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Central YAML; Path: .coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 51498bb0-4bf0-4ace-8c71-a8ac70d2a9ca

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
39154802	Triggered	Generic Password	8b18d84	SW.Bitween.UnitTests/MirrorSetupTests.cs	View secret
39154803	Triggered	Username Password	8b18d84	SW.Bitween.UnitTests/MirrorSetupTests.cs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}