This message was deleted.
# cloud
s
This message was deleted.
d
yeah, that is correct. the only thing I'll add is Egress ended callback is only made after the entire operation is complete, which includes uploading to S3. You'd get the webhook callback with EgressInfo, when the status goes to
EGRESS_COMPLETE
, it means the file upload is complete
n
@dry-elephant-14928 on testing, when participant leaves I am getting
participant_left
callback. but there is no callback received for
egress_ended
this is for egress on audio stream for a particular participant based on websocket
when 2nd participant left, then we got participant_left -> joinee participant_left -> recorder then websocket stream got disconnected egress_ended callback room_finished callback
d
I'm not following.. you just mentioned having received
egress_ended
callback above.
n
so there are 2 participants on group chain of events 1. participant A joins 2. participant A publishes audio Track a. track_published callback is received we start audio only egress 3. participant B joins 4. participant A leaves a. only participant_left callback is received 5. participant B remains alone in room for 10 more minutes 6. participant B leaves 7. egress_ended callback is received for audio stream of participant A 8. room_ended callback is received
so 7th [ egress_ended callback ] should happen within few seconds after 4.a [ A leaving ], but we only get it after 5th [ B leaves ]
d
Got it, I understand now. It sounds like
egress_ended
callback is received when the last participant left the room, when it should have been when
participant A
left. This could be an issue with Track Egress lifecycle. CC: @able-gigabyte-21598
👀 2
a
This should be fixed in the next release, there were some issues with the old webhook system
d
@nice-agent-18188 is this issue reproducible? we are not able to reproduce it on our side.
to be clear, we did improve the webhook system. but it should not have held back notifications consistently. if that's what you are experiencing, then it's likely a different issue at hand.
n
will check and revert