Detecting If There Already is A Recording Or Broadcasting With Jitsi/Jibri

I’ve gotten recording and broadcasting working as such:


 let record = room.startRecording({
                mode: JitsiRecordingConstants.mode.FILE,
                appData: JSON.stringify({
                    'file_recording_metadata': {
                        'event_id' : 'someID',
                        'jwt' : 'someJWT' // I pass the JWT of the current user, which is used to push the completed file to my API

            record.then(function (res) {
                console.log("Success Recording");
                recordSessionID = res._sessionID;
            .catch(function (err) {
                console.log("Error Recording");

Broadcasting (Streaming)

let broadcast = room.startRecording({
                broadcastId: 'someid',
                mode: JitsiRecordingConstants.mode.STREAM,
                streamId: 'rtmp://path/to/custom/rtmpservice'

            broadcast.then(function (res) {
                console.log("Success Broadcasting");
                broadcastSessionID = res._sessionID;
            .catch(function (err) {
                    console.log("Error Broadcasting");

How do you detect if recording or a broadcast (stream) for the current meeting is already happening?

Say for examples the person who started the streaming and gets disconnected. They login back in, how do they know the service is still recording? I didn’t see an obviously named function for this.

Recorders / liver streamers join as participants, though they are hidden, but you’ll still get the user joined event.

@saghul Thanks but that doesn’t quite answer the question. Let me explain it another way.

When startRecording is called, it sends a message to Jibri and return a promise. If that promise is sucessfull, there will be a a session id as such res._sessionID

How can I programmatically check if that Session recording is active or not?