Best Practices to Improve Slow Loading Times in Data Tables

Hey guys, Getting some issues with slow loading times and wondering if there are some best practices to help: . Loading columns, eg lookup other table, seems to be running a lot slower than it used to. . Making UI changes like limiting row numbers used to happen immediately, but now won't propagate unless i refresh the page. I have tried this across multiple Clay logins and across multiple browsers and seems to persist. Any pointers from the team? Cheers.

3 comments

Channeled
APP
·
·
To improve slow loading times, especially for lookups from another table, consider these best practices: 1. Be aware of rate limits: Google Sheets integrations have a default limit of 300 read requests per minute per project. Exceeding this can cause temporary blocks. 2. For large tables or complex workflows, performance issues are more likely. Try a hard refresh: • Mac: Command (⌘) + Shift + R (Chrome/Firefox) or Option (⌥) + Command (⌘) + E (Safari) • Windows: Ctrl + F5 or Ctrl + Shift + R 3. Empty spaces or "Queued" issues often occur due to loading delays or interrupted runs. Create a new column by duplicating the current one and run it on the remaining rows. 4. Filter for empty rows and run operations on those specifically. 5. Use the "merge columns" feature to combine results after running operations on filtered rows. These steps should help optimize performance and address slow loading times in your Clay tables.
Stefano
·
·
Hey, thanks for reaching out! We’re making a few changes in the app, so you may notice some temporary slowdowns. This should be resolved soon! I really appreciate your feedback—let me know if there’s anything I can help with.
Channeled
APP
·
·