Impliment automatic retry on response error

[kirkmorrow]

New Feature / Enhancement Checklist

• [ X] I am not disclosing a vulnerability.
• [X ] I am not just asking a question.
• [ X] I have searched through existing issues.

Current Limitation

Currently any temporal issue on the network connecting to the backend can cause an error condition in the Parse response. This is often easily handled by simply retrying the transaction.

Feature / Enhancement Description

Add an optional retry parameter to methods that interact with the backend. The default could be 0 for no retries (current behavior) or 1. After the retries have been exhausted and the transaction still fails, then it could return the error case.

Example Use Case

1. Application executes ParseCloudFunction and gives a retry value of 2.
2. A temporary network error causes the first transaction with the backend to return an error.
3. The retry counter is checked and found to be greater than 0.
4. The retry counter is decremented.
5. The transaction is retried and success on the second attempt.
6. The successful results are returned to the application which never sees an error condition.

Alternatives / Workarounds

An application developer can current implement retry into their own code.

[parse-github-assistant]

🚀 Thanks for opening this issue! We are excited about your ideas for improvement!