Troubleshooting JQL Query Error: Rate Limit Exceeded

Juan I. · 2025-05-13T11:33:22.121Z

im getting this error since many days now: why? Error executing JQL query: HTTP error! status: 429 - {"request": "/api/query/jql?project_id=112", "error": "Query rate limit exceeded for project_id: 112. 1/5 queries running concurrently and 61/60 queries running in the last hour. For more information, please consult our documentation at "}

Troubleshooting JQL Query Error: Rate Limit Exceeded | Mixpanel Community

5 comments

· Sorted by Oldest

kapa.ai
APP
·
·
Hi Juan I., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
You're encountering a rate limit error (HTTP 429) with your JQL query. This error occurs because you've exceeded Mixpanel's Query API rate limits.According to the error message and Mixpanel's documentation, you've hit two specific limits: 1. You've made 61 queries in the last hour, exceeding the limit of 60 queries per hour 2. You currently have 1 out of 5 allowed concurrent queries runningMixpanel enforces these rate limits to ensure system integrity and prevent any single project from monopolizing resources available to other projects.
Rate Limits for Query API
The Query API, which includes JQL queries, has the following restrictions: - Maximum of 5 concurrent queries - Maximum of 60 queries per hourRate Limits documentation confirms these limits.
How to resolve this issue
To avoid rate limiting errors, you can: 1. Spread your queries over a longer period: Reduce the frequency of your queries to stay under the hourly limit. 2. Consolidate multiple queries: If possible, combine several queries into a single, more comprehensive query. 3. Wait before retrying: Since you've exceeded the hourly limit, you'll need to wait until you're back under the 60 queries per hour threshold. 4. Implement exponential backoff: When you encounter 429 errors, use an exponential backoff strategy for retries.The Custom JQL Query documentation also mentions these limits and notes that JQL queries will timeout after 2 minutes of run-time.If you consistently need higher query limits, you might want to contact Mixpanel support to discuss your use case and potential solutions.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Juan I.
·
·
could it be there is something running in the background? havent run any call since more than 24 hours, or even days in the past and still the same error kapa.ai
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Yes, it's possible that something is running in the background that's consuming your query quota. Based on your error message showing "61/60 queries running in the last hour" despite not manually running queries for days, there are a few potential causes: 1. Automated processes: You might have scheduled reports, automated dashboards, or integrations that are making API calls to Mixpanel without your direct intervention.2. Other team members: If multiple people have access to your Mixpanel project, they might be running queries that count toward your project's rate limit.3. Third-party integrations: Any tools or services connected to your Mixpanel account could be making API calls in the background.4. Cached queries not clearing properly: Though less likely, there could be an issue with how Mixpanel is tracking your query usage.To troubleshoot this issue: 1. Check if you have any scheduled reports or automated dashboards that might be running queries. 2. Review any third-party integrations or tools connected to your Mixpanel account. 3. Check with team members who have access to the same project. 4. Consider reaching out to Mixpanel support with your project ID (112) to have them investigate if there are any stuck or persistent queries running on your account.According to the Query Result Caching documentation, Mixpanel does cache query results for varying periods depending on the date range, but this shouldn't affect your rate limits in this way.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

kapa.ai
APP
·
·
Hi Juan I., Please stand by as I search the Mixpanel knowledge base for an AI-powered answer. I normally take about 15 seconds or so. In case AI cannot answer your question, feel free to reach out to Mixpanel support at mixpanel.com/get-support. If you have follow-up questions for this thread, please tag me again with your question: @kapa.ai <follow-up question> 👋
Feel free to ask a follow-up question once I've answered by mentioning me with @kapa.ai
kapa.ai
APP
·
·
You're encountering a rate limit error (HTTP 429) with your JQL query. This error occurs because you've exceeded Mixpanel's Query API rate limits.According to the error message and Mixpanel's documentation, you've hit two specific limits: 1. You've made 61 queries in the last hour, exceeding the limit of 60 queries per hour 2. You currently have 1 out of 5 allowed concurrent queries runningMixpanel enforces these rate limits to ensure system integrity and prevent any single project from monopolizing resources available to other projects.
Rate Limits for Query API
The Query API, which includes JQL queries, has the following restrictions: - Maximum of 5 concurrent queries - Maximum of 60 queries per hourRate Limits documentation confirms these limits.
How to resolve this issue
To avoid rate limiting errors, you can: 1. Spread your queries over a longer period: Reduce the frequency of your queries to stay under the hourly limit. 2. Consolidate multiple queries: If possible, combine several queries into a single, more comprehensive query. 3. Wait before retrying: Since you've exceeded the hourly limit, you'll need to wait until you're back under the 60 queries per hour threshold. 4. Implement exponential backoff: When you encounter 429 errors, use an exponential backoff strategy for retries.The Custom JQL Query documentation also mentions these limits and notes that JQL queries will timeout after 2 minutes of run-time.If you consistently need higher query limits, you might want to contact Mixpanel support to discuss your use case and potential solutions.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
Juan I.
·
·
could it be there is something running in the background? havent run any call since more than 24 hours, or even days in the past and still the same error kapa.ai
kapa.ai
APP
·
·
Let me check the knowledge base for you again. One moment! 📚
kapa.ai
APP
·
·
Yes, it's possible that something is running in the background that's consuming your query quota. Based on your error message showing "61/60 queries running in the last hour" despite not manually running queries for days, there are a few potential causes: 1. Automated processes: You might have scheduled reports, automated dashboards, or integrations that are making API calls to Mixpanel without your direct intervention.2. Other team members: If multiple people have access to your Mixpanel project, they might be running queries that count toward your project's rate limit.3. Third-party integrations: Any tools or services connected to your Mixpanel account could be making API calls in the background.4. Cached queries not clearing properly: Though less likely, there could be an issue with how Mixpanel is tracking your query usage.To troubleshoot this issue: 1. Check if you have any scheduled reports or automated dashboards that might be running queries. 2. Review any third-party integrations or tools connected to your Mixpanel account. 3. Check with team members who have access to the same project. 4. Consider reaching out to Mixpanel support with your project ID (112) to have them investigate if there are any stuck or persistent queries running on your account.According to the Query Result Caching documentation, Mixpanel does cache query results for varying periods depending on the date range, but this shouldn't affect your rate limits in this way.
kapa.ai is still learning and improving, please let me know how I did by reacting below.
ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

5 comments

Rate Limits for Query API

How to resolve this issue

Rate Limits for Query API

How to resolve this issue