-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: reduce no-response errors in cal ai with increase of timeout threshold #11845
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@DexterStorey is attempting to deploy a commit to the cal Team on Vercel. A member of the Team first needs to authorize it. |
Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link to collect XP and win prizes! |
📦 Next.js Bundle Analysis for @calcom/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this is fine cc @emrysal
Looks like we can get away with |
What does this PR do?
Cal.ai sometimes doesn't reply to emails. We think this could be because Vercel recently changed the default timeout duration from 1 minute to 15 seconds on October 1 (and most intelligence calls take more than 15 seconds - so timeouts would be hit/miss depending on request complexity.
Requirement/Documentation
See: https://vercel.com/changelog/serverless-functions-can-now-run-up-to-5-minutes
Type of change
How should this be tested?
Send an email to cal.ai with a very simple request such as "What is my userid"
Then send an email to cal.ai with a more complex request like "What are all my meetings in the last 2 weeks?"
Second task should not respond in prod (assuming you have had a bunch of meetings)
Mandatory Tasks
Checklist
I haven't read the contributing guideMy code doesn't follow the style guidelines of this projectI haven't commented my code, particularly in hard-to-understand areasI haven't checked if my PR needs changes to the documentationI haven't checked if my changes generate no new warningsI haven't added tests that prove my fix is effective or that my feature worksI haven't checked if new and existing unit tests pass locally with my changes