Notification Delivery Failures
Know when a message failed to arrive and stop sending to addresses that cannot receive it.
What it adds
Bounce and complaint handling with a suppression list, plus telling the affected user their address is failing.
What your agent is told to do
5
What your agent is told to do
5-
1
Consume the delivery provider's webhooks for bounces, complaints, and deferrals, verify their signatures, and deduplicate repeated events by provider event ID.
-
2
Separate hard bounces and spam complaints, which suppress the address permanently, from transient failures, which retry with backoff and only suppress after a threshold.
-
3
Keep the suppression list per channel and per address, and check it before every send. Extend the existing notification preference model with delivery health rather than building a second gate beside it.
-
4
Tell the user in the app when their address is suppressed, and give them a way to correct or reverify it. An invisible suppression looks exactly like a broken product.
-
5
Do NOT let a suppressed email address block push, in-app, or SMS delivery to the same user. Suppression is per channel, never per person.
Edge cases it handles
6
Edge cases it handles
6- A spam complaint must suppress marketing and product mail without stopping password resets, and the boundary needs deciding before launch.
- Provider webhooks arrive out of order. A delivery event landing after a bounce for the same message must not clear the suppression.
- A user correcting their address must clear the suppression for the new address only, and require reverification before mail resumes.
- Admin views must show status and reason without dumping raw provider payloads, which contain recipient data and provider secrets.
- A provider-wide outage will look like thousands of individual failures — detect the pattern and avoid mass-suppressing valid addresses.
- Dead push subscriptions belong on the same failure pipeline as bounced email, not in a separate ad hoc cleanup.
Definition of done
8
Definition of done
8- Provider webhooks are signature-verified and deduplicated by event ID.
- Hard bounces and complaints suppress permanently; transient failures retry with backoff.
- The suppression list is checked before every send and is scoped per channel.
- Suppression on one channel does not affect the others.
- Affected users are told in-app and can correct and reverify their address.
- Admin views show delivery status and reason without exposing raw provider payloads.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Content Reporting
Content Reporting
Let users flag content that needs a human to look at it.
What it does
A reporting flow that captures a reason, a snapshot of context, and enough signal for a moderator — without exposing the reporter.
How it works
- 1 Add a report action to every user-generated surface: posts, comments, profiles, files, messages. Offer a short list of concrete reasons plus an optional free-text field.
- 2 Capture the context a moderator needs at the moment of reporting — the content ID, its current body, the author, and a timestamp — so the review is not dependent on the content still existing.
- 3 Give the reporter an immediate self-serve action alongside the report: hide this item, mute this author, or both. A report that takes hours to review leaves the user staring at the thing they reported.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/content-reporting
Scheduled Job Monitor
Scheduled Job Monitor
Find out a nightly task stopped running before your users do.
What it does
A record of every recurring schedule, the runs it was expected to make, and alerts when a run is missed or late.
How it works
- 1 Register every recurring task with its schedule expression, its time zone, and an expected maximum duration. A schedule that is not registered cannot be monitored.
- 2 Record the start and the completion of each run separately. A task that started and never finished is a different failure from one that never started, and they need different alerts.
- 3 Compute the expected run times forward from the schedule and compare them against actual starts. Alert on a missed run, and alert separately when a run starts on time but overruns its expected duration.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/scheduled-job-monitor
Cache Invalidation Controls
Cache Invalidation Controls
Clear stale cached data without flushing everything or restarting.
What it does
An operator control that invalidates cache entries by namespace, tenant, or resource — scoped, propagated across processes, and recorded.
How it works
- 1 Define named invalidation scopes rather than free-text key entry. An operator picks a namespace, a tenant, or a specific resource; they do not type raw cache keys.
- 2 Enforce tenancy on every scope. One workspace's operator must be structurally incapable of clearing another workspace's entries — check the scope against their permissions before building the key pattern, not after.
- 3 Propagate invalidation to every process and region that holds a copy. In-process and edge caches will not hear about a change made in a shared store unless you tell them, and a clear that only affects one server is worse than no clear because it looks like it worked.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/cache-invalidation-controls
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.