Retrying Failed Web Services Requests
If your client application receives a WS_CONCUR_SESSION_DISALLWD response or no response, retry the request after a delay.
Consider the following best practices when implementing retry logic:
-
Send the first retry attempt after a certain delay. For subsequent attempts, increase the delay between retries.
-
Avoid creating artificial concurrency peaks by synchronizing retry attempts across threads or applications. There is no recommended delay length to avoid synchronization, so choose a delay that works for your application.
-
For interactive applications, process retry attempts asynchronously to avoid requiring users to take repeated actions.
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