ConvertKit's automation canvas crawls past 40 nodes—here's why
The coffee’s gone cold in your mug, the cursor hasn’t moved in six minutes, and ConvertKit’s automation builder is rendering branches one pixel at a time while you wait for a single tag condition to appear.
ConvertKit’s automation canvas turns into molasses when your logic tree grows
The visual builder slows to a crawl past 40 nodes, forcing a choice between sequences and split automations.
ConvertKit’s drag-and-drop automation builder feels fast when you’re wiring up a welcome sequence with three emails and a tag. Add conditional branches, A/B splits, wait steps, and subscriber filters, and the canvas starts lagging. Scroll becomes choppy. Dragging a new action takes two seconds to register. Past 40 nodes, the interface is nearly unusable.
The problem isn’t your browser or your connection—it’s client-side rendering of a deeply nested visual graph. ConvertKit redraws the entire automation tree on every interaction, and performance degrades exponentially as branches multiply. The workaround is architectural: split complex automations into smaller, single-purpose flows triggered by tags, or replace visual automations with sequences wherever branching logic isn’t required. Sequences load instantly, handle thousands of subscribers without interface lag, and support basic conditional content blocks. Visual automations shine when you need real-time subscriber behavior triggers—link clicks, tag additions, product purchases—but the moment your logic exceeds a dozen decision points, the canvas becomes a liability.
The feature breakdown includes node-count thresholds, side-by-side performance timings, and a decision matrix for when to split vs. when to flatten your automation into a sequence with conditional content.
RELATED TACTIC
ConvertKit’s broadcast analytics show opens fast but clicks arrive hours later
You hit send, refresh the broadcast report, and open rate climbs in real time. Link clicks? Still at zero an hour later, even though replies mention the article you linked. ConvertKit’s analytics pipeline processes opens and clicks through different queues, and click data lags behind opens by 90 minutes to four hours during peak send windows. The delay isn’t a bug—it’s how ConvertKit’s infrastructure prioritises delivery over reporting. If you’re making editorial decisions or A/B test calls in the first two hours post-send, you’re reading incomplete data.
WORTH READING
Webhooks time out after 30 seconds and most platforms never tell you
You wire a Zapier webhook to a custom script that queries an API, enriches subscriber data, and writes it back to your CRM. It works in testing. A week later, half your automations are silently failing. Most webhook-based automation platforms—Zapier, Make, Pabbly—enforce a 30-second timeout. If your endpoint doesn’t respond within that window, the request is abandoned, often without logging a failure or sending an alert. Long-running tasks—PDF generation, third-party API calls with retries, complex database writes—exceed the limit more often than operators expect, and the failure is invisible until you audit logs manually.
FROM THE ARCHIVE
WordPress doesn’t use real cron, so scheduled posts miss their slot
You schedule a newsletter post for 6 a.m., check at 6:15, and it’s still in draft. WordPress relies on wp-cron, a pseudo-scheduler that only triggers when someone visits your site. Low-traffic sites can miss scheduled publish times by hours. High-traffic sites usually fire wp-cron reliably, but server load or caching layers can still delay execution. The fix is replacing wp-cron with system-level cron jobs that run on a true schedule, independent of visitor activity. Most managed WordPress hosts offer one-click cron replacement; shared hosting requires SSH access and a crontab edit.
Know someone who would like this? Forward today’s email — every operator we reach is one closer to running an online business with a little less friction.