Managing SCORM Settings in Bridge

Created by Richard Tobin, Modified on Fri, 13 Mar at 10:23 AM by Richard Tobin

When using SCORM courses in Bridge, it’s important to understand how runtime data is handled—especially if you rely on attempts, pass/fail logic, or re-enrolments. This article explains the Reset Runtime Data Timing setting, what each option means, and when you should use it.

What Is SCORM Runtime Data?

SCORM courses store learner progress and interactions as runtime (suspend) data. By default, this data allows learners to leave a course and return to the exact point where they left off.

While this behaviour is useful in many scenarios, it can cause issues when organizations want to:

Use attempt limits in Bridge
Ensure a course starts fresh on each attempt
Prevent learners from resuming a previously failed attempt

To address this, Bridge includes a course-level setting that controls when SCORM runtime data should be reset.

Reset Runtime Data Timing: What Does It Mean?

The Reset Runtime Data Timing setting determines when Bridge clears the stored SCORM runtime data for a learner’s next attempt.

You’ll see the following options:

1. Never (Default)

SCORM runtime data is always retained
Learners reopen the course exactly where they left off
Previous interactions, answers, and progress remain intact

TIP: Use the default option when learners should always resume where they left off, and attempts are not critical.

2. When Exit Is Not Suspend

Runtime data resets when the course exits as Complete and reports a success status (Passed/Failed). If the course exits as Incomplete or uses Suspend, runtime data is preserved. Please see our SCORM FAQs here for further information.
The next launch starts the course from the beginning
Allows Bridge to correctly register a new attempt

TIP: This is the recommended setting when using attempts.

Why this matters:
Without resetting runtime data, a learner who fails a SCORM course may reopen it in a completed or failed state, preventing Bridge from accurately tracking attempts. Resetting data ensures each attempt starts cleanly.

3. On Each New Sequencing Attempt

Runtime data resets at the start of every new sequencing attempt
The course always launches from the beginning, regardless of how it was exited

TIP: Use this when you want strict control and a fully fresh experience on every attempt.

Why the Reset RunTime Data Timing Setting Exists

By default, SCORM courses are designed to retain suspend data, which works well for resumable learning. However, this can cause challenges for customers who want Bridge to:

Enforce attempt limits
Prevent unintended unlimited retries
Ensure a failed attempt truly resets the course

To solve this, Bridge gives you the flexibility to manage this SCORM setting in the interface.

Setting PlayerResetRunTimeData = WHEN_EXIT_IS_NOT_SUSPEND ensures that when a learner completes a course (pass or fail) and exits properly, their next attempt starts fresh—allowing Bridge to accurately record attempts and outcomes.

This functionality provides more predictable behaviour and prevents courses from reopening in an already completed or failed state.

Key Takeaways

By default, SCORM courses retain progress and interactions
This can conflict with attempt tracking in Bridge
The Reset Runtime Data Timing setting gives you control over when data is cleared
When Exit Is Not Suspend is recommended when using attempts
Proper reset behaviour prevents unintended unlimited attempts and ensures accurate reporting

If you’re unsure which setting is right for your use case, or want help validating your SCORM behaviour, reach out to Bridge Support. You can see the support options available to you by clicking the ”?” in the bottom left of your Bridge instance.