I am getting an internal timeout error when trying to view a table. There are 17k records in it and I am getting this error when I try to load it. "We had an internal timeout processing your request. Please reattempt the action, or refresh the page. Adding filters or removing collection fields from the view could help if there is a lot of data. If this doesn’t work, contact us." Has anyone else seen this?
Indeed when loading so many records it times out, especially if you are showing many fields with it too.
As the error says, you can add more filters or show less fields. My main question is why you need to display 17k records at once? Or are you trying to add filters and it’s also not filtering properly?
Thanks for the speedy reply and I appreciate in advance any suggestions. I don’t need to display them. The behavior that I have seen previously is that it loads 5k records and says there are more. This is the same error I am getting when I try to retrieve one record via the API as well. It will not let me retrieve any of the records via the API even with pagination. These are time logs from clockify and I am clearing out the table and reloading it with a nightly job. Now the records load successfully, but querying them now fails.
Did you try enabling “Hierarchies Lazy Loading” in Settings → Experimental Lab?
Not yet. 
I raised the issue to the support team and either they have fixed it or it has resolved itself. Thanks!
This issue came back and I have turned the feature you recommended on to no avail. There are time entry records (17k) that I have loaded and linked to projects. I can look at the time entries by project with no issues but when I look at the full table, I get the internal timeout error rather than it just loading the first page of records. Is there a way I can change the page load behavior from the UI?
I still didn’t fully understand what you are doing which requires viewing 17k records.
Are you viewing all of them in order to delete all records and import all new records into the database from clockify?
If so, have you thought about either making a custom integration? Or if its not worth it or possible, using the “Create of Update” when importing, instead of needing to delete and reimport records.
If i misunderstood, please let me know.
Thanks Ron. I am actualy not trying to view all the records. What is happening is that when there are 18k records in the table, I start getting those internal timeout errors whenever just simply try to open the data table. I guess the behavior I am expecting is for it to load the first 100 or so records and then show how many are in the table. It does this on all of the other tables. On this table. It will not load anything and errors. When it is in that state, I cannot access it via the API either.