Retry transient Prisma initialization failures

[cursor]

Changes

• Add a small DB retry helper for transient Prisma connection/initialization errors.
• Wrap the task-create parent accessibility lookup with DB retry before notification side effects can run.
• Add Trigger retry/backoff to the DB-heavy scheduled reminder and auto-archive sweeps.
• Add focused tests for DB retry classification/behavior and cron retry configuration.

Testing Criteria

• yarn test src/utils/dbRetry.test.ts src/jobs/notifications/send-task-reminders.test.ts src/jobs/auto-archive/auto-archive-completed-tasks.test.ts --runInBand
• yarn prettier:check
• yarn lint:check (passes with existing React hook/compiler warnings)
• yarn tsc (still blocked by pre-existing src/icons/index.ts SVG module declaration errors)

Notes

• Linear and Sentry MCP access were unavailable during triage (Linear returned 401; Sentry required auth), so the exact Sentry stack/project could not be directly read. The webhook metadata shows the issue is in Triage and the title is PrismaClientInitializationError:.

Impact & Surface Area of Change

• Trigger scheduled jobs: send-task-reminders and auto-archive-completed-tasks now retry cron-level transient failures before marking the sweep failed.
• Task-create notification flow: parent-task accessibility read retries only Prisma connection/init errors before notifications are sent, limiting duplicate-notification risk.

  

[linear-code]

OUT-3932

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
tasks-app	Ready	Preview, Comment	Jun 29, 2026 9:24pm