Hi Everyone,
I have some questions about the kapsel offline plugin and how to handle retry / errors.
From the documentation i understand that once a request fails, it would be moved to the error archive and not retried. I would expect that this would also mean the change to the object would be dropped from the offline store. My plan was to then implement a retry functionality my self.
Yet when i test i see a different behavior. I have a service for pm work orders and to provoke an error i simply block an order. On the device when i try to update the order i get the expected "Order is locked by.." error. Thats fine. Now from reading the documentation i would NOT expect the offline store to retry this request the next time i flush. But his is what happens? I keep getting the error every time i flush, unless i move out of the order in the backen in witch case the update is successfull.
Can anyone comment on this behavior? Are you seeing this as well and is it documentet anywhere?
Additionally this raises som problems for me. If i get an error that cannot be resolved i have no way to discard it except for clearing the store and sync'ing a new one - not a very nice solution. Does anyone know if there is a way to remove request with error from the offline store?
Any input / comments on how you have handled this would be greatly appriciated.
Best,
Olav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.