FAQ: Why Won’t a Module Open When Assigned to a Class?

What’s the issue?

There is currently a bug affecting modules assigned directly to a Class (not within a Pathway). When a learner taps on the module, it appears unresponsive or stuck—as if it won’t open.

What’s actually happening: The module is downloading in the background, but the usual download indicator is missing, so learners don’t see any progress feedback. As a result, they may think the module is broken or frozen.

What does this look like for learners?

When a learner taps a module:

• Nothing happens, or it appears to load indefinitely.

• There is no download spinner or progress icon.

• If they tap again too quickly, the module may still not open because it hasn’t finished downloading.

This only affects modules that are:

• Assigned directly to a Class, and

• Not part of a Pathway.

How can I fix or work around this?

✅ Option 1: Use a Manual Wait-and-Retry Approach

Instruct learners to:

1. Tap the module once.

2. Wait 20–30 seconds.

3. Tap the module again.

This gives the module enough time to download silently in the background, even though no download icon appears.

✅ Option 2: Assign the Module Within a Pathway

To avoid the issue entirely:

• Reassign the module as part of a Pathway.

• Modules accessed through Pathways are not impacted, so learners can tell when it's ready.

Who is affected?

• Learners accessing modules assigned directly to a Class.

• Admins or instructors assigning modules to a class outside of Pathways.

Modules assigned via a Pathway are not affected.

Is there a fix coming?

Yes. Our engineering team is actively working on a resolution. We’ll update this article as soon as the issue is fixed.

Need help?

If you need assistance reassigning modules to a Pathway or have learners experiencing issues, contact Support.