make sure you’re on v1.4.0+ as well, there was an earlier bug where the empty timeout was not respected in this scenario

hmm yeah i tried increasing the empty timeout to 30 mins but still the same issue. i called the create room api and when i listed the rooms i saw this:

[
  {
    sid: 'RM_8vNqcPmZ4top',
    name: 'test2',
    emptyTimeout: 1800,
    maxParticipants: 2,
    creationTime: 1681846752,
    turnPassword: 'ILBFthsMxVz1irmnY0d0JJdXSs8=',
    enabledCodecs: [ [Object], [Object], [Object], [Object] ],
    metadata: '',
    numParticipants: 0,
    activeRecording: false
  }
]

but then when i created a token and joined with a user a new session replaces it:

[
  {
    sid: 'RM_MgthXZDKnTUY',
    name: 'test2',
    emptyTimeout: 300,
    maxParticipants: 0,
    creationTime: 1681846790,
    turnPassword: 'DMNeJzmrPezzbTDuVW/UbtESQh0=',
    enabledCodecs: [ [Object], [Object], [Object], [Object] ],
    metadata: '',
    numParticipants: 1,
    activeRecording: false
  }
]

with a different empty timeout