Hi @keyrllosesam158 Please report to Acumatica to increase time out https://asiablog.acumatica.com/2017/09/database-timeouts.html 

Basically the records take more time and throwing an error.

Thanks

You can also limit the record set by the transaction days into smaller chunks of data. However if you need to pull these larger data sets more frequently then adjusting timeouts is the way to go. There’s a few ways to do this and a few methodologies. Idle timeout, report query timeout and query timeout. 
 

if you’re a SaaS customer they can increase the IIS timeout, if you’re a PCS customer you can configure your idle timeout setting in the app pool in IIS. 
 

As mentioned in a previous comment:

In Acumatica we have 2 timeout for Select query:

1. Report Timeout – is used only for reports, as it may need some time to retrieve data from database for big report. To configure it you can use reportQueryTimeout=”100″ in PXSqlDatabaseProvider section of Web.config file. Parameter is defined in seconds and has default value as 30 seconds. 
2. Querry Timeout – is used only for inquires and other selects, as some inquiries also might take more time than allowed by default. To configure it you can use queryTimeout=”100″ in PXSqlDatabaseProvider section of Web.config file. Parameter is defined in seconds and has default value as 30 seconds. 

For performance and deadlock-protection reasons Acumatica does not have general timeout configurations for Insert/Update/Delete, however you can change it from code using PXCommandScope.  If you create that scope and change timeout, then the next SQL command will be executed with your timeout.

Additionally, database maintenance could help. Rebuilding/optimizing indexes for example.