Instruqt Instruqt Announcements logo
Back to Homepage

Instruqt Announcements

Latest product news and updates.

Subscribe to Updates

Labels

  • All Posts
  • Fix
  • Announcement
  • Improvement
  • research

Jump to Month

  • October 2026
  • September 2026
  • August 2026
  • July 2026
  • May 2026
  • April 2026
  • December 2025
  • September 2025
  • July 2025
  • June 2025
  • May 2025
  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • March 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • March 2023
  • January 2023
  • December 2022
  • November 2022
  • September 2022
  • August 2022
  • July 2022
  • May 2022
  • April 2022
  • February 2022
  • January 2022
  • December 2021
  • October 2021
  • August 2021
Powered by

Create yours, for free!

Improvement
2 months ago

Track limits are now Session limits

Your usage limits now cover both Tracks and 2.0 Labs in one place.

"Track Limits" is now "Session Limits." This is mainly a facelift: the protection you already rely on to guard against runaway usage hasn't changed, it now simply applies across everything you publish, whether it's a Track or a 2.0 Lab, all managed from a single view.

What it is

Session limits are guard rails on how many sessions can be started for a piece of content. Without them, anything public or embedded on a website could be launched an unlimited number of times, running up cost and inviting abuse. Limits cap that across four dimensions: per calendar month, per rolling month, per IP address per hour, and concurrent plays per IP.

It's one system covering both content types. There's a single Session Limits area, and in the management table every piece of content carries a tag showing whether it's a Track or a 2.0 Lab. One page, one set of controls, built for both.

Why it matters

  • Protects against runaway usage and cost, for all your content, Tracks and 2.0 Labs alike.
  • One place to manage everything. Tracks and 2.0 Labs live together, distinguished by a tag.
  • Safe to share widely. Publish or embed content with confidence that there's a ceiling in place.

How it works

Set a team wide default that applies across all your content, then override the limits for individual items when you need to. The management table lists every Track and 2.0 Lab together, with current values and a content type tag for each.

Limits are checked the moment a new session starts. A session that would exceed a limit is blocked, and the learner sees an informative message rather than a raw error.

Key capabilities

  • Four configurable limit dimensions: calendar month, rolling month, IP address per hour, and concurrent plays per IP
  • A team wide default with per content overrides
  • One management table for both Tracks and 2.0 Labs, each marked with a content type tag
  • Limits enforced at session start
  • A clear, informative message for learners who hit a limit

Good to know

If you know Track Limits, you already know Session Limits. Same protection, same controls, now unified under one name and one view across Tracks and 2.0 Labs.

Avatar of authorAlexander Pierce