search

daily-demos / ai-meeting-assistant

https://daily-ai-assistant-demo.vercel.app
BSD 2-Clause "Simplified" License
8 stars 2 forks source link

500 erros on `api/query` route #13

Closed chobberoni closed 8 months ago

chobberoni commented 8 months ago

Feedback

  1. After several minutes in the call we are seeing a ton of 500 errors and 504 errors when trying to query the summarizer or the question query box it also references cross origin site issues
  2. The summarizer becomes unusable and does not return anything
  3. The query box becomes unusable
lazeratops commented 8 months ago

Thanks, @chobberoni. Could you please attach your client-side logs from the session? Additionally, did this happen locally or with the deployed application? If locally, please provide the server logs as well. If deployed, approximately when did you reproduce this? I can try to find the logs in EB.

Additionally, if this was reproduced with the deployed version of the application, can you confirm whether you received the error less than 60 seconds after making the query? (I believe the Vercel request timeout is 60 seconds, so the timing will help inform if it's a Vercel timeout or a server error).

chobberoni commented 8 months ago

Thanks, @chobberoni. Could you please attach your client-side logs from the session? Additionally, did this happen locally or with the deployed application? If locally, please provide the server logs as well. If deployed, approximately when did you reproduce this? I can try to find the logs in EB.

  1. All in the production demo hosted on vercel/AWS
  2. Client-side logs -- I dd not save as I was in a real call while this happened. EB-logs will have them -- it will be the most recent session
lazeratops commented 8 months ago

The server logs from last week indicate one error: attempting to query a session that does not exist.

After checking the session in question, I confirmed that the bot was ejected as expected when the room expired. The default room expiry is 15 minutes and participants are set to be ejected by default. The bot was ejected as expected at this time. This would mean anyone trying to query this session after this time would fail, because the session no longer exists (as designed).

But the problem is that somehow participants were able to query this session despite it having been expired, and I suspect you did not ping the assistant API directly to do so (which would have explained this), right? In the dashboard, I saw some strange activity in human participants' session events for this session and will start a thread in Slack to follow up, as that is more of an underlying API question.

chobberoni commented 8 months ago

@lazeratops Got it. I did extend the expiry of the room during the call so it could have messed things up for the bot.