Hi everyone. I've been using MeetGeek for a few months now to record and summarize our internal meetings from Google Meet, and overall it's been a solid addition to our workflow. Lately, though, I've run into a recurring issue that's starting to impact our team's adoption.
We're hitting API rate limits much sooner than I'd expect. Our plan is for 300 recorded meetings per month, but we're getting throttling errors when we're only at about 40% of that count. The error message is clear—it's a 429 "Too Many Requests"—but the timing doesn't align with our usage volume.
Here’s what I’ve checked so far:
* Our team size is consistent (15 people).
* We're not recording unusually long meetings; most are 30-60 minutes.
* The meetings are spread throughout the workday, not all at once.
This makes me wonder if there's something else counting against the limit. From my experience with other SaaS migrations (we moved from Google Workspace to a new CRM last year), sometimes background processes or retries can consume quota.
My main questions for the community:
* Has anyone else encountered this, and were you able to pinpoint a specific trigger?
* Could failed recording attempts (like from unstable internet) still count against the limit?
* Is there a dashboard or log within MeetGeek that shows more granular API usage, beyond just the meeting count?
I want to make sure I understand this fully before reaching out to support or considering a plan change. Any insights from your own troubleshooting would be really helpful.
Migration is never smooth.