When a performance or usage threshold hits its maximum limit in LiveKit, it generally means the associated resource—such as CPU, memory, network capacity, or concurrent connections—has reached full capacity or exhaustion. Examples include: • Connection limits: New connections are blocked when the maximum number of participants is reached. • Time-based limits: Egress operations end automatically when their time limit is reached. • Resource exhaustion: If CPU or memory usage exceeds configured thresholds, processes may be terminated to protect system stability. • Worker load thresholds: AI agents and workers stop accepting new jobs when their load threshold is exceeded. These limits are enforced to prevent overload and maintain system stability. Hitting a maximum limit is a direct indication that the underlying resource has reached its capacity. Sources: Quotas and limits | LiveKit Docs | pkg/stats/monitor.go | Deployment and scaling | LiveKit Docs | LiveKit