Retrying Failed Web Services Requests
If your client application receives the WS_CONCUR_SESSION_DISALLWD response, or you do not receive any response, you should retry sending the request after a certain period.
Consider the following best practices when implementing retry logic:
-
You should send the first retry attempt after a certain delay. If more attempts are needed, you should increase the delay between attempts.
-
Avoid the creation of artificial concurrency peaks due to synchronized retry attempts from different threads or applications. There is no specific preferred length of delay between retry attempts to avoid synchronization.
-
If retry attempts are needed for interactive applications, you should execute requests asynchronously so there is no need for repeated user action.
Related Topics
- Web Services and RESTlet Concurrency Governance
- Concurrency Governance Limits Based on Service Tiers and SuiteCloud Plus Licenses
- Concurrency Governance for Internal Applications
- Effects of Authentication Method on Concurrency Governance
- Account Concurrency Monitoring Resources
- Errors Related to Concurrency Violations
- Best Practices
- Sample Scenario
- Frequently Asked Questions