trpc-query-that-writes-violates-idempotency-contract

Using a tRPC query procedure (GET semantics) to perform writes — such as checkDueTomorrow creating notification records — violates the query/mutation contract and causes silent data integrity issues. Queries are expected to be idempotent reads; only mutations should produce side effects. Beyond the semantic violation, reminder delivery becomes user-triggered rather than scheduled, meaning reminders never fire unless a user actively hits the endpoint. All write operations must be tRPC mutations; background jobs must be driven by an actual cron, not by API calls.

Related

• trpc-query-used-for-write-violates-idempotency
• trpc-query-writing-data-violates-idempotency-contract
• trpc-query-used-for-write-violates-idempotency-contract
• trpc-query-writing-side-effects-breaks-idempotency
• trpc-query-used-for-writes-breaks-reminder-delivery
• trpc-query-procedure-used-for-writes-contract-violation
• trpc-query-used-for-write-cron-notification-never-fires
• trpc-query-that-mutates-state-antipattern
• trpc-query-that-writes-is-silent-cron-failure