Push delivery hygiene: expiry + dead-subscription pruning

[codebestia]

Handle 410 Gone/404 from the push service by disabling/removing dead subscriptions. Track lastUsedAt. Back off on transient failures to prevent sending to stale endpoints forever.

Acceptance criteria:

• 410/404 responses prune the subscription
• Transient failures retried with backoff
• Metrics on push success/failure

[jabir-dev788]

@jabir-dev788 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hey, I’d love to work on this issue if it’s available ‎I've reviewed this issue and have a clear approach to fix it. I can deliver a clean, minimal PR within 5 hours without touching unrelated code. Happy to take this on if it's still available.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jabir-dev788 to this issue.

[modecodes]

@modecodes has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this, and i can submit the pr with 48hr

ℹ️ Repo Maintainers: To accept this application, review their application or assign @modecodes to this issue.

[Depo-dev]

@Depo-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day team, my name is Depodev, I have gone through the issue requirements and i am confident i can deliver and i will like to work on this.

ETA: 24 hrs

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Depo-dev to this issue.

[Chidimj]

@Chidimj has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Clicked team,

I have experience building backend systems that prioritize reliability, observability, and efficient resource management. I've worked on notification services where handling stale endpoints, retry strategies, and monitoring delivery success are essential for maintaining healthy push infrastructure while minimizing unnecessary network requests.

For this issue, I'll implement logic to automatically prune subscriptions that return permanent errors such as 404 and 410, while introducing exponential backoff for transient failures to avoid repeatedly targeting unavailable endpoints. I'll also track subscription activity through a lastUsedAt timestamp and expose success and failure metrics to provide better visibility into push delivery performance and subscription health.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chidimj to this issue.

[drips-wave]

Congratulations, @Chidimj! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Chidimj: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊