🚧 Downgrade Experience: Query Blocked by “Too Many Requests” Error

We're currently investigating an issue affecting some users after they downgrade their subscription plans.

🧾 What Happened?

A user downgraded from an Enterprise plan to a Professional plan and was unexpectedly blocked from running queries — even after just a single request. The error displayed:

“Too many requests, try again later”

The user also reported confusion around when their downgrade would take effect, expecting continued access to the higher-tier features until their billing cycle ended — since they had already paid for it.

✅ Expected Behavior:

• Users who downgrade should still:

  • Retain access to their original (higher-tier) plan limits until the end of their billing cycle.

  • Be able to run queries according to the correct current plan limits.

⚠️ Current Behavior:

• Users may be rate-limited incorrectly right after downgrading.

• Downgrade timing and access changes are not clearly communicated.

• This creates confusion and may lead to loss of trust or churn.

🔧 Proposed Fixes:

• ✅ Investigate and correct rate-limiting logic for downgraded users.

• ✅ Ensure users retain functionality from their previous plan until the billing cycle ends.

• ✅ Improve in-app messaging during plan changes to clearly explain:

  • What features are retained

  • When the new plan limits take effect

We’re working to resolve this ASAP and will post an update here once fixed. Thanks for your patience! 🙏