Why does LINQ not guarantee idempotent query execution in distributed environments?

LINQ itself is idempotent only in pure in-memory scenarios; distributed execution introduces state and timing dependency.

In distributed systems, query results depend on external state, network timing, and eventual consistency. LINQ does not enforce idempotency guarantees. Re-executing the same query can produce different results if underlying data changes between executions.