Hi, Gregory

- Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

- We noticed a couple of errors in the console, for example, this error 400 as a bad Admin-Ajax response:

These errors can happen for a few reasons.

Check if you have any errors, notices, warnings in your console. If there are, resolve them first because they are interrupting wpDataTables' admin-ajax calls and the errors returned are referring to either bad Ajax or bad JSON response.

Another thing that could be causing this is cache. If the data is being cached on the page, the returned data is not the same, or not at least what wpDataTables is expecting to see, so the error occurs. Try clearing all cache from your website and browser, and then prevent the pages containing wpDataTables from being cached.

Last, it could be the data in the table(s) - if the data is not the type that it should be (for example, a non-numerical value in an integer or a float column), or if the data has been changed for a formula column. Try creating a new table from the source table and see if it's going to cause errors. If it doesn't (after excluding cache as the cause), look for differences between data, filters, etc.

-

- Also, if you solve the console errors, wanted to additionally advise for the loading speed.

We noticed that this table is JSON-based, and seems like you have more than 3 thousand rows in it.

If your data set is quite large (many thousands of rows), using the JSON format for creating a wpDataTable would not be a good solution, since the page generation time and size would significantly increase. MySQL-based wpDataTables with server-side processing is always the best option for large datasets.

- Please contact us further if you tried all mentioned above, and we will do the best we can to assist.