Skip to content

bug: Session length setting not respected - getting 3 problems instead of configured 5 #249

@smithrashell

Description

@smithrashell

Summary

After changing session length setting to 5 problems, sessions are still being created with 3 problems (the previous setting).

Expected Behavior

When session length is set to 5, new sessions should contain 5 problems.

Current Behavior

Sessions still contain 3 problems even after changing setting to 5.

Possible Causes

  1. Max vs Target: Setting might only control maximum, not target session length
  2. Cache Issue: Old setting cached somewhere and not refreshed
  3. Adaptive Logic: Adaptive session length algorithm overriding the setting
  4. Problem Availability: Not enough eligible problems to fill session

Questions to Investigate

  • Is the setting stored as "max_session_length" or "target_session_length"?
  • Does the adaptive algorithm use this as a ceiling or a goal?
  • Is there a cache that needs to be cleared when settings change?

Steps to Reproduce

  1. Change session length setting to 5
  2. Complete current session
  3. Start new session
  4. Observe session contains 3 problems instead of 5

Labels

bug, settings

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions