Skip to main content
Solved

Read Timeout fetching data even when using $skip and $top parameters

  • June 17, 2025
  • 2 replies
  • 65 views

Litox
Freshman I

I'm trying to download JournalTransaction data. I'm following the documentation to Retrieve the List of Records in Batches, using the $top and $skip parameters. I've tried different values for those.

But I can see that as the $skip parameter grows each request take increasingly longer to finish.

Finally, after ~1 hour of processing, it fails with a ReadTimeout. Even if I retry, after 60 secs or more, it keeps failing with ReadTimeout. It is not a session expiration issue: I tried with logout/login.

Besides it is not consistent. For example with a $size of 500 it typically fails on $skip=115500. But sometimes I get up to the next page ($skip=116000) until it fails.

And I can't get over that.

Any ideas?

Best answer by ruchikasharma23

Hi ​@Litox 
This looks like a known issue, ETA for fix : 2025R2.
Clients can experience performance issues on Journal Transactions (GL301000) when loading a large batch linked to projects.

As a workaround, could you please try to add the following index and let us know if it helps.
CREATE NONCLUSTERED INDEX usrPMBudget1 ON [dbo].[PMBudget] ([CompanyID],[ProjectTaskID])

 

2 replies

Forum|alt.badge.img+3
  • Acumatica Moderator
  • Answer
  • June 17, 2025

Hi ​@Litox 
This looks like a known issue, ETA for fix : 2025R2.
Clients can experience performance issues on Journal Transactions (GL301000) when loading a large batch linked to projects.

As a workaround, could you please try to add the following index and let us know if it helps.
CREATE NONCLUSTERED INDEX usrPMBudget1 ON [dbo].[PMBudget] ([CompanyID],[ProjectTaskID])

 


Litox
Freshman I
  • Author
  • Freshman I
  • June 17, 2025

Hi ​@Litox 
This looks like a known issue, ETA for fix : 2025R2.
Clients can experience performance issues on Journal Transactions (GL301000) when loading a large batch linked to projects.

As a workaround, could you please try to add the following index and let us know if it helps.
CREATE NONCLUSTERED INDEX usrPMBudget1 ON [dbo].[PMBudget] ([CompanyID],[ProjectTaskID])

Thanks for the information! It really helps to understand that's not something on my side.

Until I can try to implement what you propose, I changed the pagination strategy and instead of top+skip I'm using filters to bring batches of data based on a date range. It seems to be working for now...