OUT-3730 | Trigger.dev job: send-task-reminders scheduled task

[arpandhakal]

Changes

• Add src/jobs/notifications/send-task-reminders.ts — Trigger.dev schedules.task running at 0 0 * * * (00:00 UTC) that walks eligibility, fans out company tasks, writes the dedupe ledger, and dispatches reminder emails.
• Add src/jobs/notifications/send-task-reminders.test.ts — 7 tests covering empty input, IU filtering, happy path, re-run idempotency, company fan-out, Copilot-failure compensation, per-workspace isolation.
• Register sendTaskReminders in src/jobs/notifications/index.ts so Trigger.dev's dirs auto-discovery picks it up.

Implements OUT-3730.

Per-workspace flow

1. Group eligibility rows by workspaceId; filter out assigneeType='internalUser' (kept in the cron rather than the SQL so OUT-3736's contract stays untouched).
2. prisma.task.findMany to fetch { id, title, createdById } for the workspace's task ids.
3. Mint a per-workspace CopilotAPI from any task's createdById + workspaceId via encodePayload — same shape as cmd/backfill-missed-emails. Resolve the Workspace once per workspace.
4. For each eligibility row, resolve recipients: client rows stay 1:1; company rows fan out via copilot.getCompanyClients(assigneeId). Members no longer in the company drop out naturally.
5. Single batched ledger INSERT (per ticket spec, verbatim):

   INSERT INTO "TaskReminderSents" (...)
   VALUES ...
   ON CONFLICT ("taskId", "recipientId", "reminderType") DO NOTHING
   RETURNING ...

   Only rows returned by RETURNING are net-new claims to send.
6. For each net-new row: call sendReminderEmail. On Copilot failure → DELETE FROM "TaskReminderSents" WHERE id = ? so the next cron run retries. A failing DELETE is logged distinctly (permanent miss).

Idempotency boundary

Ledger insert happens before the send. The unique constraint guarantees that a retry, an in-flight duplicate, or a manual re-trigger can never double-send.

Concurrency

• Bottleneck({ maxConcurrent: 5 }) for workspaces, matching WORKSPACE_CONCURRENCY in auto-archive-completed-tasks.ts.
• Promise.allSettled for the workspace loop so a failing workspace doesn't abort the sweep.
• Sequential within a workspace — per-workspace volume is low (tens, maybe hundreds), and per-workspace Copilot rate limits favor sequential.

Testing Criteria

• yarn test src/jobs/notifications/send-task-reminders.test.ts — 7/7 passing.
• yarn test src/jobs/notifications/send-reminder-email.test.ts — 5/5 still passing (unchanged).
• npx tsc --noEmit — 0 errors project-wide.
• npx prettier --check on the new + modified files — clean.
• Deferred to OUT-3732 — staging dry-run, validate against a real database, monitor first three 00:00 UTC runs.
• Deferred to OUT-3731 — fixture-based eligibility SQL tests (mocks here cover the cron's control flow, not the underlying SQL).

Notes

• Base branch is OUT-3737, not feature/email-reminders — stacked PR so reviewers see only the cron diff here.
• Depends on OUT-3737 (sendReminderEmail), OUT-3736 (getEligibleReminders), OUT-3735 (getReminderEmailDetails), OUT-3734 (TaskReminderSents + enum).
• senderId = task.createdById (the IU who created the task) is the chosen identity; flag in review if reminders should use a different sender.
• IU eligibility rows are filtered in the cron rather than the SQL. Reason: keeps OUT-3736 untouched. We pay one extra row per IU-assigned task per day in the eligibility result, which is negligible.
• The cron does not register itself with index.ts for the IU-only delete-task-notifications pattern — it's a schedules.task, picked up automatically by dirs: ['./src/jobs'] in trigger.config.ts. The index.ts export is for symmetry with the other notification triggers.

Impact & Surface Area of Change

• Net-new cron, off by default until the Trigger.dev schedule registers in production. Zero impact on existing notification flows.
• New DB writes go only to TaskReminderSents (OUT-3734). No reads/writes to ClientNotification, InternalUserNotification, ActivityLog, or Task.
• New Copilot calls: getWorkspace + getCompanyClients (once per workspace), createNotification (one per send). All wrapped in the existing withRetry.
• Watch the first three production runs (OUT-3732 covers monitoring): per-workspace [X/Y] workspace ws_…: sent N, failed M, skipped K log + final sweep summary.

🤖 Generated with Claude Code

[linear-code]

OUT-3730

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	May 26, 2026 3:00pm

[greptile-apps]

Greptile Summary

Adds a new Trigger.dev scheduled cron job (send-task-reminders) that runs daily at 00:00 UTC, walks eligible (task, assignee, reminderType) rows, fans company-assigned tasks out to individual members via Copilot, writes a deduplication ledger using an INSERT … ON CONFLICT DO NOTHING … RETURNING pattern, and dispatches reminder emails — compensating the ledger on send failure so the next run retries.

• Core idempotency is sound: the unique constraint on (taskId, recipientId, reminderType) is the dedupe primitive; RETURNING correctly identifies net-new rows; ledger compensation on Copilot error is implemented and tested.
• Per-workspace concurrency uses Bottleneck({ maxConcurrent: 5 }) + Promise.allSettled for workspace-level isolation, matching the existing pattern.
• Fan-out error isolation has a gap: a getCompanyClients failure inside the plan-building loop propagates out of processWorkspace, causing the workspace-level catch to fire and silently abandoning any client-assigned tasks that appeared after the failing row in that workspace's batch.

Confidence Score: 3/5

Safe to merge only after addressing the getCompanyClients error-propagation issue; a transient Copilot failure for one company row will silently drop reminders for unrelated client-assigned tasks in the same workspace.

The idempotency design, ledger compensation, and workspace-level isolation are all solid. The gap is in the plan-building loop inside processWorkspace: a thrown error from getCompanyClients bubbles out of the entire function, causing the workspace-level catch to fire and abandoning any client-assigned rows that come after the failing company row. This is a real present defect on the changed path that the test suite does not exercise.

src/jobs/notifications/send-task-reminders.ts — specifically the plan-building for loop around resolveRecipients.

Important Files Changed

Filename	Overview
src/jobs/notifications/send-task-reminders.ts	New scheduled Trigger.dev cron job. Core idempotency logic (ledger INSERT … ON CONFLICT) and workspace fan-out are correct, but the plan-building loop leaves company-row getCompanyClients errors unhandled per-row, which can abort an entire workspace and silently skip otherwise-healthy client-assigned tasks.
src/jobs/notifications/send-task-reminders.test.ts	Good coverage of the main paths (empty input, IU filter, happy path, idempotency, company fan-out, ledger compensation, workspace isolation). The getCompanyClients-throws scenario is not tested, so the per-row propagation bug is not caught here.
src/jobs/notifications/index.ts	Trivial export addition; no issues.

Sequence Diagram

sequenceDiagram
    participant Trigger as Trigger.dev (00:00 UTC)
    participant Job as send-task-reminders
    participant DB as Prisma / Postgres
    participant Copilot as CopilotAPI

    Trigger->>Job: run(payload)
    Job->>DB: getEligibleReminders()
    DB-->>Job: allRows (incl. IU rows)
    Job->>Job: filter out internalUser rows
    Job->>Job: group by workspaceId

    loop Each workspace (up to 5 concurrent via Bottleneck)
        Job->>DB: task.findMany
        DB-->>Job: tasks [id, title, createdById]
        Job->>Copilot: new CopilotAPI(encodePayload(...))
        Job->>Copilot: getWorkspace()
        Copilot-->>Job: workspace

        loop Each eligibility row (sequential)
            alt "assigneeType = company"
                Job->>Copilot: getCompanyClients(assigneeId)
                Copilot-->>Job: members[]
                Note over Job: fan out 1 plan entry per member
            else "assigneeType = client"
                Note over Job: 1 plan entry 1:1
            end
        end

        Job->>DB: INSERT INTO TaskReminderSents ON CONFLICT DO NOTHING RETURNING
        DB-->>Job: inserted rows (net-new only)

        loop Each net-new ledger row
            Job->>Copilot: sendReminderEmail
            alt success
                Note over Job: sent += 1
            else Copilot error
                Job->>DB: taskReminderSent.delete
                Note over Job: failed += 1
            end
        end
    end

    Job-->>Trigger: sent, failed, skipped, workspaceCount

Loading

_{Reviews (1): Last reviewed commit: "feat(OUT-3730): add send-task-reminders ..." | Re-trigger Greptile}

[vercel]

Deployment failed with the following error:

Deploying Serverless Functions to multiple regions is restricted to the Pro and Enterprise plans.

Learn More: https://vercel.link/multiple-function-regions

[priosshrsth]

@arpandhakal I would suggest to have better variable naming in send-task-reminders.ts if possible.

[priosshrsth]

@arpandhakal Can we simplify this?