Notice that this will may result in non-idempotent mutations being resent to the server. Re-trying a SetCell() mutation where the server selects the timestamp can result in multiple copies of the data stored with different timestamps. Only use this policy if your application is prepared to handle such problems, for example, by only querying the last value and setting garbage collection policies to delete the old values.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["The `AlwaysRetryMutationPolicy` retries all mutations, which may lead to non-idempotent operations being resent to the server, potentially creating multiple copies of data with different timestamps."],["This policy is suitable when applications can handle the potential issues of multiple data copies, such as by querying only the last value and implementing appropriate garbage collection policies."],["The `AlwaysRetryMutationPolicy` class offers functions to clone the policy (`clone()`) and to determine if a mutation or conditional mutation is idempotent (`is_idempotent()`)."],["This documentation provides versioned reference for the `AlwaysRetryMutationPolicy`, with version 2.37.0-rc being the most recent, and versions going as far back as 2.11.0."]]],[]]
