Long Loading Times for Lookup: Support Team Assistance Needed

Long loading times for lookups can be caused by several factors. Try a hard refresh first: - Mac: Command + Shift + R (Chrome/Firefox) or Option + Command + E (Safari) - Windows: Ctrl + F5 or Ctrl + Shift + R Performance issues often occur with larger tables or complex workflows running simultaneously. Empty spaces and loading delays are common with larger datasets. For Google Sheets lookups specifically, there's a 300 read requests per minute limit that can cause temporary blocks. Wait a minute and retry the request. If using API integrations, check your tier limits - lower tiers may require processing smaller batches (around 50 rows at a time).

This is likely due to API tier limits. With lower tier APIs (like tier 1), you need to process data in smaller batches of around 50 rows at a time. To process larger datasets: ** Break large data requests into smaller batches ** Monitor your usage limits, tiers and API quotas * Performance issues are more common with larger tables or complex workflows running simultaneously You can check your API limits in your provider's settings (e.g., Anthropic console) to understand your current tier restrictions.

For 24-hour lookup issues, try a hard refresh first: ** Mac: Command + Shift + R (Chrome/Firefox) or Option + Command + E (Safari) ** Windows: Ctrl + F5 or Ctrl + Shift + R Long loading times are often caused by: ** Large tables or complex workflows running simultaneously ** API tier limits requiring smaller batches (around 50 rows at a time) * Google Sheets API hitting the 300 requests per minute limit - wait a minute and retry Break large requests into smaller batches and monitor your API usage limits and quotas. Empty spaces and loading delays are common with larger datasets.

I think you might have what you need here, so I'll tentatively mark this closed for the moment. Please keep in touch if you hit other roadblocks!