Scheduled Job Monitor
Find out a nightly task stopped running before your users do.
What it adds
A record of every recurring schedule, the runs it was expected to make, and alerts when a run is missed or late.
What your agent is told to do
7
What your agent is told to do
7-
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.
-
4
Deduplicate alerts per schedule. One ongoing outage is one incident — send a notification when it opens, optionally a reminder, and one when it recovers. Do not fire an alert per missed run.
-
5
Support marking a schedule as intentionally paused, with who paused it and why, and suppress its alerts while paused.
-
6
Do NOT alert on the first late run of a schedule that has never successfully run. A newly deployed task with a wrong expression should surface as unconfigured, not as an outage.
-
7
Live queue state, payload inspection, and manual retry are owned by Background Job Dashboard; link across to it rather than duplicating queue controls here.
Edge cases it handles
7
Edge cases it handles
7- Daylight-saving transitions delete one local hour and repeat another. A schedule set for that hour must not silently skip or double-fire, and the monitor must not report the skip as a miss.
- Store and compare in UTC, but display in the schedule's own time zone. An operator debugging a 02:00 job needs to see 02:00.
- A schedule changed mid-week invalidates the historical expectation. Version the schedule and evaluate each past run against the expression in force at the time.
- The monitor itself can fail. If the checking process stops, nothing is reported as missed — treat a stale monitor as an alertable condition of its own.
- A run that overlaps the next scheduled run needs a policy: skip, queue, or run concurrently. Show which one applies.
- Failure reasons shown on the dashboard must be redacted the same way job payloads are — a stack trace from a nightly export routinely quotes customer data.
- A schedule deleted from the code must not alert forever. Mark unregistered schedules as retired rather than missing.
Definition of done
9
Definition of done
9- Every recurring task is registered with its schedule, time zone, and expected duration.
- Starts and completions are recorded separately, and overruns alert distinctly from misses.
- Each schedule shows last success, next expected run, last duration, and last failure reason.
- One ongoing incident produces one alert plus a recovery notification.
- Paused schedules suppress alerts and record who paused them.
- DST transitions produce neither a false miss nor a double run.
- A stopped monitoring process is itself detectable.
- 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
Notification Delivery Failures
Notification Delivery Failures
Know when a message failed to arrive and stop sending to addresses that cannot receive it.
What it does
Bounce and complaint handling with a suppression list, plus telling the affected user their address is failing.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/notification-delivery-failures
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.