trpc-query-used-for-writes-contract-violation

A tRPC query procedure (GET) used to both check reminders AND write notification records violates the idempotent-read contract for queries. Additionally, reminder checks implemented as queries only fire when a client calls the endpoint — there is no background cron triggering them. Reminder/notification side-effects must be mutations, and background delivery requires a separate cron or job queue.

Related

• trpc-query-must-not-write-data
• trpc-query-must-not-write-side-effects
• trpc-query-used-for-write-ops-breaks-reminder-delivery
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-used-for-side-effects-breaks-idempotency-contract
• trpc-query-procedure-must-not-perform-writes
• trpc-query-that-writes-is-broken-notification-pattern