Course platforms queue, reject, or lie when uploads break
The progress bar sits at 94 per cent for twenty minutes, then vanishes. No error message, no queued notification, no file in your dashboard. You refresh twice, check your browser console, and wonder whether the 4 GB webinar recording ever left your machine.
Course platforms handle oversized video files three completely different ways
Teachable, Kajabi, and Thinkific each break, queue, or fail silently when you exceed their upload limits.
Every course platform advertises generous file-size caps—2 GB here, 5 GB there—but the boundary behaviour varies wildly. Teachable silently accepts your upload, then returns a generic error thirty seconds after the progress bar completes. Kajabi queues oversized files for manual review, which sounds helpful until you realise “review” means a support ticket and a three-day wait. Thinkific cuts you off mid-upload with a client-side warning, but only if you’re using Chrome; Safari users see the same phantom progress bar that plagued Teachable.
The differences matter when you’re launching a course on a fixed schedule. One platform lets you retry immediately with a compressed file. Another logs your attempt as “pending” and blocks subsequent uploads to the same lesson slot until support clears the queue. A third charges your bandwidth quota even when the upload fails, which means you’ve burned 4 GB of your monthly allowance on a file that never went live. None of this appears in the marketing comparison charts, and most operators only discover the failure mode when they’re twelve hours from launch and the final module won’t publish.
The post walks through what each platform does at the boundary, which error states recover automatically, and when to compress before you upload instead of hoping the platform’s transcoder will fix it server-side.
PARALLEL PROBLEM
Social schedulers silently skip rows when your bulk CSV has formatting errors
You upload two hundred posts in a single CSV, the scheduler reports “198 queued successfully”, and you assume the other two are typos you can fix later. Most platforms never tell you which rows failed or why—malformed dates, missing image URLs, and emoji encoding problems all trigger silent skips. Buffer, Hootsuite, and Later each handle corrupt rows differently: one logs the failure in a downloadable report you’ll never notice, one queues a placeholder post with broken media, and one simply decrements the success count. If you’re scheduling a product launch or a timed campaign, two missing posts can break the entire narrative arc.
MIGRATION RISK
Mailchimp’s export CSV drops tags, automation history, and segment rules
Switching from Mailchimp to ConvertKit or Beehiiv feels straightforward until you import the CSV and discover half your subscriber metadata is missing. Mailchimp’s standard export includes email addresses and basic fields, but tags live in a separate file, automation trigger history isn’t exported at all, and segment logic exists only as Mailchimp’s proprietary conditions—there’s no portable format. If you’ve been tagging subscribers by lead magnet, purchase history, or engagement tier, you’ll need to document those rules before you export, then rebuild them manually in the new platform. Most operators realise this two weeks after migration, when they try to send a segmented campaign and find a thousand subscribers sitting untagged.
DIAGNOSTIC TIP
WordPress plugin conflicts write logs to three different locations
When two plugins collide and your site breaks, WordPress rarely shows an error on the front end—it just stops rendering content or redirects to a blank page. The actual conflict gets logged, but where depends on your host, your PHP version, and whether WP_DEBUG is enabled in wp-config.php. Some hosts write to /wp-content/debug.log, others use the server’s error_log in your root directory, and a few pipe everything to a custom dashboard you didn’t know existed. If you’re troubleshooting a white screen or a broken checkout flow, knowing where to look cuts diagnosis time from thirty minutes to three. The post maps out where each major host writes logs and which error patterns reveal plugin conflicts versus theme issues.
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.