trpc-query-procedures-must-be-idempotent-reads-only

tRPC query procedures (GET semantics) must be pure reads. Using a query procedure to write notifications or trigger side effects (e.g., reminders.checkDueTomorrow writing notification rows) violates the GET/query idempotency contract and causes reminders to fire only when a user manually calls the endpoint. Scheduled side-effect logic must live in mutation procedures triggered by a cron, not in queries.

Related

• trpc-query-used-for-write-ops-breaks-reminder-delivery
• trpc-query-must-not-write-data
• trpc-query-must-not-write-side-effects
• trpc-query-used-for-side-effects-breaks-idempotency-contract
• salesforce
• 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-used-for-side-effectful-reminder-writes
• trpc-query-procedure-used-for-side-effecting-writes
• trpc-query-writing-data-breaks-cron-and-idempotency
• trpc-query-that-mutates-violates-idempotency-contract
• trpc-query-with-write-side-effects-breaks-idempotency
• trpc-query-used-for-write-violates-idempotency-contract
• trpc-query-procedures-must-not-write-data
• trpc-query-used-for-write-violates-idempotency
• trpc-query-procedure-with-write-side-effects-breaks-reminder
• trpc-query-writing-data-violates-idempotency-contract
• trpc-query-procedure-performing-writes-contract-violation
• trpc-query-used-as-mutation-breaks-reminder-delivery
• trpc-query-with-side-effects-breaks-idempotency
• trpc-query-used-for-write-operations-breaks-idempotency-cont
• trpc-query-that-writes-is-silent-cron-failure