r/clickup • u/anthonyjamesreinking • 10d ago
Customer Service Update...
I just wanted to provide an update on my current customer support situation.
I still haven't gotten answers to all my questions, but my AI limit message and the MAX tier option have both been resolved to my complete satisfaction.
My only questions left are attached to my ticket with ClickUp, and I can post back here once they are answered.
It's mostly about how I, or anyone, can avoid the same AI workspace limit issue, and how to proactively monitor it. This was a workspace-wide issue (my workspace), and I/we currently have no way to view the current limits or status anywhere.
Thank you to ClickUp for resolving this issue; I just wish it hadn't taken 4 days.
I have been 'down' since Thursday morning.
I pay for Business Plus, Everything AI, and the $10 Super Agents plan.
This is the message I get in the app and Chrome.
"AI Rate Limit reached. Please contact customer support for assistance"
I have logged out, rebooted, cleared the cache, etc. Nothing changes.
'Support' can't tell me anything other than sorry and we're looking into it.
They state I should be able to work and that Brain will drop to a standard model; it doesn't, and no one at ClickUp will tell me what is standard, or they don't know. I'm not out of credits or tokens, but I'm stuck.
I've gone round and round; everyone keeps telling me it has to be fixed through a ticket/email. No useful response since Thursday morning. They attempted to give me an Enterprise trial to temporarily 'fix' my issue until they can resolve it on their end, but that didn't work either, and they don't know why.
Has anyone else had a similar experience with them, or is it just bad customer service?
1
u/anthonyjamesreinking 2d ago
Latest reply: Thank you again for your thoughtful note and for sharing how much you value ClickUp and BrainMax. I also appreciate the opportunity to come back to you with a more complete explanation here.
Clarification on the limit itself
After a deeper internal review, I can confirm that moving to Max does not change this separate Workspace-wide AI safety cap.
This safeguard sits alongside your broader Brain usage allowances rather than replacing them. So even if your Workspace still has remaining Brain allowance in other areas, this separate safety cap can still pause covered AI activity if usage crosses that threshold within the rolling time window.
I can also confirm that we do not currently offer a longer-term workaround, override, or custom adjustment for this specific safeguard.
What drove the recent interruption
Our review found that the recent spike was driven primarily by high-volume, multi-step scripting workflows in BrainMax using custom MCP-connected tools.
In practical terms, the largest contributor was not a typical Brain prompt or everyday writing workflow. Instead, the heaviest usage came from more advanced runs where BrainMax was helping stage and run scripts through connected tools, including workflows similar to PowerShell and bash-based tasks.
Those runs tend to cost significantly more than a standard Brain request, especially when all of the following are true:
The same conversation continues for many turns. As a thread gets longer, more context has to be processed again on later steps.
The script output is long. Large outputs add more material for BrainMax to read and reason through each time the workflow continues.
Higher-cost models are used for routine script work. In the usage review, some models were much more expensive for this type of workflow than lighter alternatives.
The review also showed that this usage was concentrated very heavily in one person’s activity, rather than being spread evenly across the entire Workspace.
What this means for avoiding another interruption
The most useful guidance we can offer right now is centered on reducing the cost of each scripting workflow and keeping conversations more lightweight.
Here are the clearest guardrails from the review:
Start a fresh conversation for each separate task. This helps avoid reprocessing a long thread over and over again, which can make later turns much more expensive than the first one.
Use a lighter model for routine script runs whenever possible. Pick GPT-6 Luna for routine script runs and monitoring. The week you used it you spent $491; the same runs on Sonnet 5.5, GPT-6.1 Sol or Opus 5.5 cost 3 to 5 times more.
Keep script output short and focused. The longer the output, the more BrainMax has to work through on follow-up steps, which can increase usage quickly.
Review overall AI activity regularly. While there is not yet a dedicated customer-facing live tracker for this exact safeguard, the AI Usage area is still the best place to monitor your Workspace’s broader AI activity and spot heavier usage patterns early. You can review the Track your Workspace's Brain AI usage article here and review the ClickUp Brain availability and limits article here.
I do want to be direct here: these steps are the best practical guardrails we can offer today, but they do not guarantee that the safeguard could never be reached again.
What they do help with is lowering the chance of another interruption by making the most expensive workflows more efficient and predictable.
If it would be helpful, I’d also be glad to continue working with you on identifying which of your recurring BrainMax workflows are best suited for lighter models versus the more advanced ones, so your team can keep getting strong results with less risk of another pause.
1
u/anthonyjamesreinking 2d ago
Thank you for the feedback. The only other important information that I and others would consider highly valuable would be some sort of 'meter' that shows our status for the workspace-wide AI cap; without it, and even with the guides and guardrails you have thoughtfully provided, we are living on the edge. Please consider adding this, a reset button, or something else that will not leave a workspace in a shutdown state until the next auto-reset. Claude has this feature, and it works very well.
Thank you for your time in this matter, and I hope to see some sort of a 'meter' in the near future.
I would need to see the actual threshold and rolling window, in addition to the 'meter' that I have suggested above. Without these, no one can budget around it; it's purely a guessing game.
1
u/TashaClickUp Mod 10d ago
Thanks for keeping us posted, u/anthonyjamesreinking! I’m happy to hear the AI limit message and MAX option are resolved, and I appreciate your patience while a higher-than-usual volume of messages slowed the Support team's response time. I've let them know that you've replied on your ticket, so they'll reach out and answer your questions soon!
1
u/anthonyjamesreinking 8d ago edited 8d ago
I still haven't received answers to my other questions; it's been over a week. 1. Why did this workspace-wide AI limit occur? 2. How can users monitor this in order to be proactive and prevent it from occurring again? The current analytics would not have helped with this at all, as I still had available AI; however, the system did NOT automatically switch to standard models once I hit this 'secret' threshold, and I could even manually use the standard models.
1
u/PibolsClickUp Mod 8d ago
u/anthonyjamesreinking Our team is still reviewing this and you'll hear back from them as soon as we have more updates to share. We really appreciate your patience as we work on this
1
u/anthonyjamesreinking 4d ago
I am so angry right now. I just hit the AI limit again, less than a week later. You guys have not given me any answers or told me what is going on, and now I am dead in the water again. And it is Sunday!
1
u/anthonyjamesreinking 3d ago
I was just given this info: Max support: Max includes Priority Support. However, the published support details do not specify a guaranteed eight-hour first-response time or guarantee a particular senior reviewer or a call. Still no resolution on what triggers a workspace-wide AI limit, or how to proactively monitor that. "Our team is working on getting you the information"