Without knowing the specific issue you're referring to, I can't identify what triggered it. Common triggers for various Clay issues include: invalid emails causing waterfall providers to run sequentially, formula assumptions about data availability, security measures for spam prevention, browser cache issues, incorrect API configurations, missing data formatting, and performance impacts from large tables or simultaneous operations.
Could you describe the specific issue or error you're experiencing so I can help identify what triggered it?
.png){kind=logo}
