This guide explains how to skip challenges within a track.
Skipping challenges allows learners to skip a challenge within a track. This might be useful when learners are stuck on a certain challenge or have partially completed a track and want to pick up where they left off.
Who can skip challenges?
If every challenge in a track has a solve script, users can potentially skip challenges. The following users can always skip challenges:
All team members.
Additionally, anyone can skip challenges if the Allow skipping __ setting is checked on the track.
All or nothing
If you enable skipping for learners, they will be able to skip every challenge in a track.
Before you begin
There are two requirements to enable the skip a challenge feature for a track:
Click the TRACK_NAME of the track where you want to enable skipping.
↳ Instruqt shows the corresponding Track overview page.
Turn on the Allow skipping toggle.
↳ The toggle looks like this now:
If the Allow skipping toggle is grayed out or disabled for your track, ensure that every challenge with a check script also has a solve script.
Open the track.yml file of the track where you want to enable skipping in your code editor.
Add or adjust the following property to track.yml:
Save track.yml and open a terminal where you enter:
instruqt track push
↳ Instruqt CLI pushes your track with skipping enabled to the Instruqt platform.
Now inform your learners that they can skip a challenge by clicking Skip when playing the track.
Force skipping is skipping to a specific challenge without running any lifecycle script. This can be useful when you debug challenges. You can only force skipping from Web UI and need to be one of the track authors: