This message was deleted.

cc @able-gigabyte-21598 @great-umbrella-58130

Your yaml config looks right. Can you verify that an HPA was created on your cluster? And can you also check the CPU usage reported by the HPA?

For 2, room composite using our templates, or track/track composite should all end when the room ends. If you're using custom templates with room composite, you need to call the EndRecording helper function from the template sdk (usually whenever the last person leaves the room) We also have a bug (recently fixed, but not yet released) where if the egress never starts, and the room is deleted without anyone ever joining, it will hang indefinitely. Do any of these sound like your situation?

@able-gigabyte-21598 That makes sense. We’re using a custom template, and sending start/end console logs directly (instead of using the sdk). I assume the end log never fired on the instances that hung; thanks for your help!

logging directly should still work, as long as it’s exactly

END_RECORDING