trpc-query-procedure-with-write-side-effects-breaks-reminder

trpc-query-procedure-with-write-side-effects-breaks-reminder-delivery

A tRPC query procedure (reminders.checkDueTomorrow) that writes notification records violates the idempotent-read contract and means reminder delivery only happens when a client manually calls the endpoint. Without a cron job driving the query, reminders are silently never sent. Reminder/scheduled-notification logic must live in a mutation or server-side cron, never in a query.

Related

• trpc-query-procedure-used-as-mutation-violates-contract
• trpc-query-procedure-used-for-side-effecting-writes
• trpc-query-used-for-write-ops-breaks-reminder-delivery
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-must-not-write-data
• trpc-query-used-for-write-operations-breaks-idempotency-cont