Long processing times are common with multi-step waterfall enrichments, but 4+ hours for 2K rows means something is likely misconfigured. Here's how to diagnose and fix:
1. Check for table complexity issues. Large tables with multiple enrichment columns running simultaneously cause severe slowdowns. Multiple actions running at once, tables linked together in a workbook, and resource-intensive features like "write to table" all compound.
2. Reduce concurrent enrichments. Don't run all columns at once. Run enrichment steps sequentially: company data first, then people search, then email finding, then verification. Each step feeds the next.
3. Break large tables into batches. Instead of 2,000 rows in one table, run 200-500 at a time. Tables can get stuck loading for 8+ hours with no progress indicator when they're too large.
4. Check for stuck waterfalls. When waterfalls show as "queued" with no results, try a hard refresh (Cmd+Shift+R on Mac) or toggle auto-update off and on.
5. Skip unnecessary steps. Use conditional logic: if the company domain is already known, skip company enrichment. If you already have a verified email, skip the email waterfall entirely. This can cut processing time by 50%+.
6. Check API rate limits. If you're using external APIs, their rate limits may be throttling your workflow. Apollo limits to 200 calls per minute for example. Build in appropriate delays.
Expected benchmarks: A well-optimized waterfall (company enrich > people search > email waterfall > verification) should process around 200-500 rows per hour depending on provider response times.