trpc-query-used-for-write-violates-idempotency

tRPC queries (GET contract) must be idempotent reads — using a query procedure to trigger writes (e.g. reminder notifications via checkDueTomorrow) violates the protocol contract and means side effects only fire on client-initiated calls, not scheduled jobs. Write operations that should run on a schedule must be mutations called from a cron worker, not queries.

Related

• trpc-query-procedure-must-not-perform-writes
• trpc-query-procedure-used-for-side-effecting-writes
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-used-for-side-effects-reminder-anti-pattern
• trpc-query-used-for-write-violates-idempotency-contract
• trpc-query-that-writes-silent-reminder-anti-pattern
• trpc-query-that-writes-violates-idempotency-contract