Chime Meeting ended automatically when 2nd attendee joined

[Kick933]

Checkboxes for prior research

• [X] I've gone through Developer Guide and API reference
• [X] I've checked AWS Forums and StackOverflow.
• [X] I've searched for previous similar issues and didn't find any solution.

Describe the bug

ChimeMeetingId -: 8c3d37b4-40a3-49c8-b1a1-6af28fc02954

when the second attendee joined this meeting, it automatically ended for some reason. All following API requests after adding mediacapturepipeline to the meeting resulted in error saying-: Meeting not found

This is unexpected. Though, I am using NodeJS 14, but still, this should not happen. The meeting events also show that the both attendee joined meeting.

SDK version number

"@aws-sdk/client-chime-sdk-media-pipelines": "^3.468.0", "@aws-sdk/client-chime-sdk-meetings": "^3.468.0",

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

NodeJS 14

Reproduction Steps

Only happened for 1 meeting. Unable to reproduce the error.

Observed Behavior

All calls after the two attendees joined resulted in meeting not found error given by SDK.

Expected Behavior

The calls should suceed

Possible Solution

No response

Additional Information/Context

No response

[RanVaknin]

Hi @Kick933 ,

Without seeing any code, logs or errors it's really difficult to advise you. I'm not familiar with the Chime API, but when a user joins the session there should be a log, either in the form of a request / response through the SDK, or a Cloudtrail event.

Can you please provide a sample code example and articulate where in the code youre seeing the failure?

Thanks, Ran~

[github-actions[bot]]

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.

[Kick933]

We are yet to find the root cause for this. It wouldn't help closing this issue. It has not happended again. But we still think that finding the root cause is important for us. Chime SDK on our NodeJS application does not log. However, we have mediaCapturePipeline meeting events to clarify that two attendees joined. Howeve, as the 2nd attendee joined, the meeting ended automatically without any trigger from our end. We have verified that we did not initiate the end meeting call by going through our logs. We have verified that the 2nd attendee did join by our logs as well as by meeting events. We have also verified that the meeting ended as soon as the 2nd attendee joined. Would the meeting-events help in finding the issue?

[aBurmeseDev]

Hello @Kick933 - checking in here. I understand your previous response from February, indicating that the reported behavior is no longer occurring. However, I would like to inquire if there have been any new developments or reoccurrences of the issue.

If you require further assistance in investigating the root cause, it would be beneficial if you could provide a minimal code snippet or sample that can reproduce the problem. Additionally, any relevant logs or request data you can share would greatly aid our analysis.