You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As describe on #3259 , mutation errors can happen for various reasons.
Even through the DataStore does its best effort to replay mutations in case of errors, sometimes mutations can't be replayed and in this case the DataStore content is no longer the same as the server content with no way to correct it.
Describe the solution you'd like
A nice feature would be to help developers to replay or correct failed mutations.
Few ideas to do that :
add a mutationErrorHandler to DataStoreConfiguration which can force a mutation to be kept by datastore giving a retry delay, a retry priority (if other mutations should be sent before this one will be retried) or something like that
persist a "mutation on error" list which can be consult and easily retried
...
Describe alternatives you've considered
Actually, to "replay" mutation we follow this flow :
clear the DataStore
wait it to be full sync
compare it with our local base and replay all missing creates / updates / deletes again (using DataStore.save/delete )
Is the feature request related to any of the existing Amplify categories?
DataStore
Additional context
No response
The text was updated successfully, but these errors were encountered:
This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you!
Is your feature request related to a problem? Please describe.
As describe on #3259 , mutation errors can happen for various reasons.
Even through the DataStore does its best effort to replay mutations in case of errors, sometimes mutations can't be replayed and in this case the DataStore content is no longer the same as the server content with no way to correct it.
Describe the solution you'd like
A nice feature would be to help developers to replay or correct failed mutations.
Few ideas to do that :
DataStoreConfiguration
which can force a mutation to be kept by datastore giving a retry delay, a retry priority (if other mutations should be sent before this one will be retried) or something like thatDescribe alternatives you've considered
Actually, to "replay" mutation we follow this flow :
DataStore.save/delete
)Is the feature request related to any of the existing Amplify categories?
DataStore
Additional context
No response
The text was updated successfully, but these errors were encountered: