trpc-query-must-not-write-data

tRPC query procedures have GET semantics and are expected to be idempotent reads. Placing write operations (e.g., sending notifications, creating reminder records) inside a query means they only execute when a client explicitly calls the endpoint — no scheduler will fire them. Reminder or notification delivery logic must live in mutation procedures called by a cron job, not in queries.

Related

• trpc-query-used-for-side-effects-breaks-idempotency-contract
• trpc-query-must-not-write-side-effects
• trpc-query-used-for-write-ops-breaks-reminder-delivery
• docker
• salesforce
• trpc-query-procedures-must-be-idempotent-reads-only
• trpc-query-used-for-writes-contract-violation
• trpc-query-procedure-must-not-perform-writes
• trpc-query-procedure-used-as-mutation-violates-contract
• trpc-query-writing-side-effects-breaks-idempotency
• trpc-query-that-mutates-violates-idempotency-contract
• trpc-query-with-write-side-effects-breaks-idempotency
• trpc-query-procedure-with-write-side-effects-breaks-reminder