Best Practice - Multi-Tenant Cloud Server Timeout Limit

Introduction

As part of our ongoing efforts to stabilize the cloud multi-tenant environments and improve user response times, we’ve introduced a new 1-minute timeout limit for requests that reach the database. This change helps keep the system balanced so that a single API’s long running or repeated requests do not affect performance across tenants, ensuring smoother and more reliable access for all users.

What's Changed

When a request is sent through API it first passes through WebLogic and security layers. Once the request reaches the database, it must be completed within one minute. If the process exceeds this limit, the request will automatically time out.

What to Expect

If a request times out, you may see an error message such as 503 (Service Unavailable) or 504 (Gateway Timeout). This typically indicates that multiple resource-heavy requests were sent simultaneously from the same IP address, overwhelming the server’s capacity to respond in time.

Recommendation

• Use finders or pagination parameters like limit and offset to filter the number of requests sent at any given time. For guidance on implementing pagination and using finders effectively, please refer to Best Practice | Data Filtering requirements.
• If a timeout is experienced, wait and try back later, instead of concurrent retries.
• Contact CMiC Support if the timeout persists after waiting and adjusting URL filtering parameters.