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
Currently, when a download fails in Moly, users are shown an error message with a button to retry manually. This requires user intervention and doesn’t account for temporary network issues or other transient errors (specially annoying for big downloads when using VPNs).
Proposed Solution
Implement an automatic retry mechanism for failed downloads. This feature should include the following:
Retry Attempts:
Attempt to retry failed downloads automatically up to 3 times.
Backoff Strategy:
Introduce increasing wait times between retries. Suggested intervals are:
15 seconds before the first retry.
30 seconds before the second retry.
60 seconds before the final retry.
User Feedback:
Update the error popup during each retry attempt to display a message like “Retrying in X seconds.” This will provide clear feedback to the user on the current retry status.
Final State
If all retries fail, the app should revert to the standard error message with a retry button, allowing the user to manually intervene if needed.
The text was updated successfully, but these errors were encountered:
@joulei Hello,I’ve completed this issue and tested it,it works fine. #289
However, due to some timing issues with the cx.start_timeout on Linux, it hasn’t met the expected results yet. You might need to fix the problem on Makepad first.
Problem
Currently, when a download fails in Moly, users are shown an error message with a button to retry manually. This requires user intervention and doesn’t account for temporary network issues or other transient errors (specially annoying for big downloads when using VPNs).
Proposed Solution
Implement an automatic retry mechanism for failed downloads. This feature should include the following:
Attempt to retry failed downloads automatically up to 3 times.
Introduce increasing wait times between retries. Suggested intervals are:
Update the error popup during each retry attempt to display a message like “Retrying in X seconds.” This will provide clear feedback to the user on the current retry status.
If all retries fail, the app should revert to the standard error message with a retry button, allowing the user to manually intervene if needed.
The text was updated successfully, but these errors were encountered: