Hi Shweta,

please check below link.

https://success.outsystems.com/documentation/outsystems_developer_cloud/monitoring_and_troubleshooting_apps/manage_technical_debt_in_odc/performance_findings/long_server_requests_timeout/

Hello @shweta chaudhari.

Go to service center and go the application where that module is, then click on operations tab and set the Server Request Timeout and apply.

Be awere this will affect all modules from the application.

Regards

Gonçalo Almeida

Hallo @shweta chaudhari  , 

I think you need to look for the cause, not the solution.

You can look for the parts that take a long time and break them down into smaller sections. For example, if 1,000 items are being retrieved from the database and causing the issue, you can divide them into multiple smaller batches.

You can also check light processes, as they might help.

You may also need to check the Execution Plan in SQL to see if the timeout is caused by a slow query.

Hello.

Increasing the "Server Request Timeout" will prevent timeouts from happening on the OutSystems side, but will not make the action end faster.

It will not make things faster as it depends mostly on the other side, like Kerollos said.

Finally, AI Mentor is simply stating that users don't want to wait long for an answer. Even if you find the right number for it not to fail is 2 minutes, do you think a user wants to wait that long? Better change that connection to an asynchronous process and later retrieve it to the screen.

@shweta chaudhari : Your application is timing out, so you increased the 'Server Request Timeout' to fix it. However, AI Mentor Studio flagged this as an issue, and you want to resolve it.

The solution is to identify and fix the root cause of the timeout while keeping the default timeout setting. If resolving the issue isn’t possible, mark it as 'Won’t fix' and proceed.