Performance Issues with Large Data Volume in Clay: Is This Normal?

Hi all, I am currently using Clay on the Explorer plan and I running into performance issues with larger data volumes (10k rows). The table I am currently using is processing three columns - Debounce, Chat GPT, and Smartlead Add Lead to Campaign (all using my own API keys). This has been processing very slowly, often leaving many rows as “queued” and having to be re-triggered. Is this normal behaviour? At this rate it will be quicker to run my sheets through Debounce and upload to Smartlead outside of Clay.