Live on prod, 0 of 8 surfaces working, less than a day left
Sep 20, 2026, 12:04 PM
Behaviors Libra is checking
Using the remind-me action creates or updates an email task with task type `follow-up` instead of the removed `reminder` type.Inconclusivelow confidence
Verification reached its 130s outer budget before the verifier returned. Libra is keeping this intent verifying until the next check.
prod, checked Sep 20, 2026, 12:04 PM
Using the mail “remind me” action creates or updates an accepted `follow-up` task while preserving the reminder description, email channel, due date, and task output data.Inconclusivelow confidence
Verification reached its budget before a verdict.
staging, checked Sep 21, 2026, 12:05 AM
A mail reminder only updates its own previously created reminder task, identified by the `source='remind-me'` provenance marker, instead of overwriting an unrelated user-created follow-up on the same conversation and thread.Inconclusivelow confidence
Verification reached its budget before a verdict.
staging, checked Sep 21, 2026, 12:06 AM
The `reminder` task type is no longer accepted, advertised, or permitted by task creation APIs, agent task tooling, admin commands, or the `user_tasks.task_type` database constraint.Inconclusivehigh confidence
Since 2026-09-18T19:03:16Z in staging, telemetry contains only low-volume read/list evidence: userTasks.listUserTasks (3 related spans, HTTP 200, p95 ~724 ms, 1 distinct user) and userTasks.getTaskById (4 related spans, HTTP 200, p95 ~100 ms, 1 distinct user), plus one.
staging, checked Sep 21, 2026, 1:07 AM
Repeated remind-me actions re-find and update only their own thread task, without overwriting an ordinary user-created follow-up on the same conversation and thread.Not checked
prod
The `reminder` task type is no longer exposed or accepted by task APIs, the task tool, the task-admin CLI, or the `user_tasks` database constraint.Not checked
prod
Failures attributed to this change
No prod customers are affected while this is only in staging. If promoted, prod impact is unknown because Libra still needs a concrete exception, route, and failed user action before assigning severity. 0 hits · no retained affected-user count · no retained trace sample.Introducedmedium confidence
internal_only
staging, first seen Sep 18, 2026, 2:10 PM
No prod customers are affected while this is only in staging. If promoted, prod impact is unknown because Libra still needs a concrete exception, route, and failed user action before assigning severity. 0 hits · no retained affected-user count · no retained trace sample.Introducedmedium confidence
internal_only
staging, first seen Sep 18, 2026, 2:34 PM
No prod customers are affected while this is only in staging. If promoted, prod impact is unknown because Libra still needs a concrete exception, route, and failed user action before assigning severity. 0 hits · no retained affected-user count · no retained trace sample.Introducedmedium confidence
internal_only
staging, first seen Sep 18, 2026, 4:00 PM
No prod customers are affected while this is only in staging. If promoted, prod impact is unknown because Libra still needs a concrete exception, route, and failed user action before assigning severity. 0 hits · no retained affected-user count · no retained trace sample.Introducedmedium confidence
internal_only
staging, first seen Sep 18, 2026, 10:35 PM
No prod customers are affected while this is only in staging. If promoted, prod impact is unknown because Libra still needs a concrete exception, route, and failed user action before assigning severity. 1 hit · no retained affected-user count · no retained trace sample.Introducedmedium confidence
internal_only
staging, first seen Sep 19, 2026, 9:48 AM
Libra found 8 production surfaces on prod but could not judge any of them yet. 4 surfaces had under 20 requests, so Libra has not judged them; 4 surfaces had no requests at all. Libra checks hourly for 3 days after each deploy.
Summary
Every create-task call with taskType: 'reminder' has been failing since the feature shipped (2026-05-26): the app-level TASK_TYPES enum allowed it, but the migration adding it to the live user_tasks_task_type_check constraint (0039_add_reminder_task_type.sql) was never applied to prod. Confirmed via prod: zero task_type='reminder' rows have ever existed , both the user-facing "remind me on a thread" feature and agent-created follow-ups (e.g. next-steps) silently lost the task every time, retrying up to 4x against the same deterministic failure and firing a Slack alert each time.
Rather than apply the missing migration, this removes 'reminder' as a task type outright:
It has no production data to preserve.
The in-flight task-axes migration (apps/mail/modules/userTasks/TASK_AXES_DESIGN.md) already treats 'reminder' as having no long-term home , its own backfill mapping files it under the "Follow-ups" task group, and its divergence notes say it becomes other once task_type is eventually dropped.
task_type itself is still live (~111 files still read it; the migration's Phase 8b/9 to drop the column is deferred/gated, stalled since 2026-08-23), so this isn't blocked on that larger migration finishing.
Changes
aop-schema.ts , removed 'reminder' from TASK_TYPES, TASK_TYPE_DESCRIPTIONS, and the Drizzle check() definition, which now matches the live prod constraint exactly.
mail.ts's upsertReminderTaskForConversation (the one real write path) , now writes taskType: 'follow-up' instead, matching the task-groups migration's own reminder -> Follow-ups mapping. Tightened its lookup predicate with taskCreatedBy: 'user' so it can't collide with agent-created follow-up tasks on the same thread.
schemas.ts, taskTool.ts , removed 'reminder' from the agent-facing tool descriptions.
user-tasks.ts, task-admin/cli.ts , removed independent 'reminder' enum copies (not derived from the canonical TASK_TYPES).
services/user-tasks/tasks.ts , doc comment.
mail-remind.test.ts , updated the one test asserting the old (always-failing) behavior.
Left untouched: DailyRecapCategory in recap-helpers.ts/admin.ts and its downstream display-category branches , independently typed, not TaskType-derived, so they don't break; they just become permanently unreachable now that no row can ever have task_type='reminder' again. Optional follow-up cleanup, not part of this PR.
Show production surfaces and changed-file mappingHide production surfaces and changed-file mapping
Production surfaces
Surface
Requests
Errors
p95
Users
Verdict
model_chunk Next Steps and Tasks Manager
131 → 5
0 → 0 (0%)
1 ms → 7 ms
0
Insufficient traffic
5 requests, under the 20 Libra needs
/api/trpc/userTasks.listUserTasks
6 → 3
0 → 0 (0%)
6248 ms → 724 ms
0
Insufficient traffic
3 requests, under the 20 Libra needs
/api/trpc/userTasks.getTaskById
0 → 3
0 → 0 (0%)
not measured → 101 ms
0
Insufficient traffic
3 requests, under the 20 Libra needs
model_step Next Steps and Tasks Manager
70 → 2
0 → 0 (0%)
36136 ms → 11832 ms
0
Insufficient traffic
2 requests, under the 20 Libra needs
POST /api/trpc/userTasks.listUserTasks
4 → 2
0 → 0 (0%)
6248 ms → 724 ms
0
Insufficient traffic
2 requests, under the 20 Libra needs
invoke_agent Next Steps and Tasks Manager
36 → 1
0 → 0 (0%)
65219 ms → 22857 ms
0
Insufficient traffic
1 request, under the 20 Libra needs
execute_tool list-tasks
1 → 1
0 → 0 (0%)
292 ms → 59 ms
0
Insufficient traffic
1 request, under the 20 Libra needs
mail.setRemind
0 → 0
0 → 0 (0%)
not measured
0
No traffic
No requests recorded since this deploy.
mail.setRemind
0 → 0
0 → 0 (0%)
not measured
0
No traffic
No requests recorded since this deploy.
/api/trpc/userTasks.listUserTasks
0 → 0
0 → 0 (0%)
not measured
0
No traffic
No requests recorded since this deploy.
POST /api/trpc/userTasks.listUserTasks
0 → 0
0 → 0 (0%)
not measured
0
No traffic
No requests recorded since this deploy.
/api/trpc/userTasks.getTaskById
0 → 0
0 → 0 (0%)
not measured
0
No traffic
No requests recorded since this deploy.
model_chunk Next Steps and Tasks Manager
16 → 0
0 → 0 (0%)
1 ms → not measured
0
No traffic
No requests recorded since this deploy.
model_step Next Steps and Tasks Manager
7 → 0
0 → 0 (0%)
18588 ms → not measured
0
No traffic
No requests recorded since this deploy.
invoke_agent Next Steps and Tasks Manager
1 → 0
0 → 0 (0%)
24843 ms → not measured
0
No traffic
No requests recorded since this deploy.
execute_tool list-tasks
1 → 0
0 → 0 (0%)
459 ms → not measured
0
No traffic
No requests recorded since this deploy.
Changed files → surfaces
apps/server/src/services/user-tasks/tasks.tsmodel_chunk Next Steps and Tasks Manager/api/trpc/userTasks.listUserTasks/api/trpc/userTasks.getTaskByIdmodel_step Next Steps and Tasks ManagerPOST /api/trpc/userTasks.listUserTasksinvoke_agent Next Steps and Tasks Manager+8
apps/server/.claude/skills/cedar-configuration/fields-and-values.mdno production surface mapped
apps/server/src/db/aop-schema.tsno production surface mapped
apps/server/src/mastra/tools/task/schemas.tsno production surface mapped
apps/server/src/mastra/tools/task/taskTool.tsno production surface mapped
apps/server/src/task-admin/cli.tsno production surface mapped
apps/server/src/trpc/routes/__tests__/mail-remind.test.tsno production surface mapped
apps/server/src/trpc/routes/mail.tsno production surface mapped
apps/server/src/trpc/routes/user-tasks.tsno production surface mapped
Reminders overwrite user follow-ups <a href="https://github.com/CedarCopilot/cedar-mail/pull/2822#discussion_r4049