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-14 UTC."],[[["The latest version available is 2.37.0-rc, with numerous older versions down to 2.11.0 also listed."],["The `AlwaysRetryMutationPolicy` retries all mutations, which may result in non-idempotent mutations being resent to the server."],["This policy is designed for applications that can handle potential issues, such as multiple copies of data with different timestamps, typically by only querying the last value."],["The `AlwaysRetryMutationPolicy` class has functions to check if a mutation or a conditional mutation is idempotent."],["The AlwaysRetryMutationPolicy class contains a function to return a copy of the policy."]]],[]]
