Why Tracks can't be nested inside other Tracks — and the automation pattern that delivers what nesting would have done.
Learning Tracks can't contain other Learning Tracks. That's an intentional product design choice, not a missing feature: a Track is meant to be a single coherent pathway for a learner, and nested Tracks would create branching, ambiguous paths that hurt completion rates more than they'd help organization.
The content types a Track can contain are Articles, Files, Videos, Assessments, and SCORM. If you're trying to put a Track inside another Track, you almost always actually want one of two things: a longer Track with Sections (organizational structure inside a single Track), or a sequence of Tracks triggered by an automation (Track A assigned, then Track B when Track A completes). This article covers the automation pattern.
The Automation Pattern
Instead of nesting, chain Tracks together with an automation. When a learner completes Track A, the automation assigns Track B automatically. The learner experiences a continuous learning path; the program admin gets independent reporting on each Track.
Step One. Navigate to Admin > Automations. Select the audience type — the best fit for chaining Tracks is usually A user has completed content or A user has completed an assignment. Pick whichever matches your trigger and enter the Track or assignment that should kick off the next one.
Step Two. Under the Content tab, select the next Track (or Tracks) to assign when the trigger fires. For informal recommendations where completion doesn't need to be tracked, use the Share option instead of Assign.
Step Three. Complete the remaining automation setup steps, then activate the automation. Until activated, the automation doesn't fire — even if the trigger conditions are met.
When to Use Sections Instead
If the reason you wanted to nest Tracks was "this Track is too long, I want to group its content," the answer is Sections, not nesting. Sections divide a single Track into named groups of content without creating a separate Track. Learners see one Track with clear chunks; you get one set of completion data.
Reach for the automation pattern only when the chained content genuinely is a separate Track — distinct enough to have its own reporting, its own due date, or its own audience.
Where This Fits
You're here because you tried to add a Track to another Track and Continu didn't let you. The structural alternative — Sections within a single Track — lives in Add a Learning Track. The sequencing alternative — automation-chained Tracks — lives in Creating an Automation.
See Also
- Tracks and Journeys: Designing Learning Paths — the strategic anchor.
- What is a Learning Track? — the gateway article.
- Add a Learning Track — building a Track, including Sections.
- Creating an Automation — the automation pattern that replaces nesting.
- Activate an Automation — the final step before an automation fires.
Tracks don't nest. Use Sections to chunk a long Track, or an automation to chain separate Tracks together when one completes.