All Docs
FeaturesCSI Teachable Replacement AppUpdated March 15, 2026

Import Error Handling & Partial Failure Recovery

Import Error Handling & Partial Failure Recovery

Available from v1.0.62

The Teachable import pipeline now handles errors at the individual lesson and asset level. A single failure — such as a broken asset URL or an unparseable lesson page — no longer aborts the entire import job. Instead, the pipeline records the failure, skips the affected item, and continues processing the rest of your content.

How It Works

When the import engine encounters an error on a specific item, it:

  1. Catches the error at the lesson or asset boundary rather than letting it propagate up and terminate the job.
  2. Logs the failure with the item identifier, error type, and a human-readable error message.
  3. Continues processing all remaining lessons and assets in the course.
  4. Reports a partial_success status when the job completes and at least one item failed.

Import Statuses

StatusMeaning
successAll lessons and assets imported without errors.
partial_successImport completed, but one or more items failed. Review the error log.
failedThe import job itself could not complete (e.g. authentication error, school unreachable).

Reading the Error Log

After an import finishes with a partial_success status, the import report includes a Failed Items section. Each entry contains:

  • Item type — lesson or asset
  • Item identifier — the lesson title or asset URL that failed
  • Error type — e.g. DownloadTimeout, ParseError, UnsupportedFormat
  • Error message — a description of what went wrong

Use this log to identify which content needs attention. Common remediation steps:

  • Asset download failure — verify the source asset URL is still accessible in the origin Teachable school, then re-run the import.
  • Parse error — check the lesson page for unusual formatting or unsupported embed types and simplify the content before re-importing.

Behaviour Before v1.0.62

Prior to this release, any unhandled error during an import would immediately terminate the entire job and mark the whole import as failed. All successfully processed lessons up to that point were still saved, but no further content was imported, and the job had to be re-run from scratch.

No Configuration Required

This behaviour is enabled automatically for all imports. No settings changes or migration steps are needed.