Skip to main content

Enroll into an Upcoming Scheduled Offering of a Track

Learn the nuances of the scheduled track autorule

Chris Ramlow avatar
Written by Chris Ramlow
Updated over 2 weeks ago

Overview of the Rule

  • The rule "Enroll into an upcoming scheduled offering of a track" is designed to enroll users into the next available scheduled instance of a specific track, not into a parent track itself

  • Scheduled tracks are essentially single-use copies of a main track, each with specific event dates (e.g., "Onboarding 6/1/2025"), rather than enrolling users in the evergreen or parent track template.

How It Works

  • When triggered, the rule looks for the next available scheduled offering (i.e., a scheduled track that hasn't started yet) and enrolls users into that instance.

  • If there is no upcoming scheduled track available (for example, if the only scheduled track has already started), the rule fails to enroll users.

  • The rule does not enroll users in the parent track itself, only in its scheduled offerings.

Clarifications from the Discussion

  • Tracks can contain content items but not events directly; instead, event types are added to tracks, and scheduled tracks are created with specific events based on those types.

  • The confusion arose because some users were enrolled while others were not, which was traced back to the lack of an upcoming scheduled track for the rule to use.

  • There is a separate rule, "Enroll into all upcoming events of a track," which enrolls users into all future events associated with a track, but this does not enroll them in the track itself.

Observed Issues

  • Failures reported in the system were not due to the rule logic itself, but rather to a bug that occurred after enrollment: a logging action was crashing, so the system never marked the enrollment as successful even though it completed.

  • If some events in the scheduled track are already past, the rule may enroll users only in the remaining upcoming events, potentially leading to partial enrollments and further confusion.

Key Takeaways

  • The rule is working as intended: it enrolls users only in the next available scheduled offering of a track, not the parent track.

  • Failures seen in the logs are due to a post-enrollment bug, not the enrollment logic itself.

  • To ensure successful enrollments, there must be a future scheduled track available; otherwise, the rule will not take effect

Summary Table

Did this answer your question?