Retries stop if user is offline for a few hours. Queue is then also blocked for any new mutations.

[doldyn]

Note: If your issue/feature-request/question is regarding the AWS AppSync service, please log it in the
official AWS AppSync forum

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Retries stop if user is offline for a few hours. Queue is stuck and any new mutations afterwards are also stuck. Users unable to post from device.
I believe the issue relates to the default retry strategy in redux-offline which AppSync leverages. The default strategy after 10 min is to wait for 30 min, then 1 hour and nothing after that.
redux-offline has an option to parse specific retry strategies as well as other important features such as specific ways to determine if online. Redux-offline is however wrapped in the AppSync Store without the option to parse redux-offline parameters. A possible solution would be to change the default strategy in AppSync but a more flexible solution would be to expose the redux-offline configuration options as part of creating the AppSync client. This would allow for use of redux-offline as intended.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
In any App, go offline and make mutations. Then wait for several hours to go online. Once online, queued mutations are no longer posted.
What is the expected behavior?
Queued and new mutations are posted once connectivity is restored.
Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions?
React.js. Any version.

[undefobj]

Could you post a gist or other sample code with your application setup? We are unable to reproduce this and have tested with both API Key and Cognito User Pools authentication strategies.