Hi @lucid gust. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
#Usage limit disabled
vestal lanternBOT
Based on the knowledge sources, I can share some relevant information about how spending limits work in Convex, though I don't have enough detail to fully explain your specific billing discrepancy.
How Spending Limits Work
Convex's spending limits function as follows: [Team billing]
- The warning threshold is a soft limit — it only sends an email notification but does not stop usage.
- The disable threshold is a hard limit — when exceeded, all projects in the team are disabled.
Importantly, spending limits only apply to resources used beyond what's included in your plan. Seat fees (per-developer charges) are not counted toward the limit.
Why You Might Have Exceeded the Cap
A few things to be aware of:
- The limit may not have been set as a hard "disable" threshold — if it was set as a warning threshold, it wouldn't have stopped usage automatically.
- Seat fees are excluded from the spending limit calculation, so those costs accumulate regardless.
- There can be edge cases, such as the race condition mentioned in one support thread, where billing state and usage tracking can get out of sync. [Subscription upgrade]
What to Do
The knowledge sources indicate that Convex's team is generally understanding about unexpected billing spikes, especially from attacks or bugs, and will work with users rather than sending surprise large bills. [Billing risk]
I'd strongly recommend contacting Convex support directly ([email protected] or via the dashboard) to get a detailed breakdown of the charges and resolve the discrepancy, as this specific billing issue goes beyond what I can diagnose from the available documentation.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
lucid gust
...
See progress here: xx/data?showSchema=true
Checking that documents match your schema...
How long will this take and does this cost me money?
@vestal lantern
vestal lanternBOT
Let me check the knowledge base for you again. One moment! :books:
Sorry @lucid gust, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
lucid gust
@vestal lantern ...
See progress here: xx/data?showSchema=true
Checking that documents match your schema...
How long will this take and does this cost me money?
vestal lanternBOT
Let me check the knowledge base for you again. One moment! :books:
The message you're seeing — "Checking that documents match your schema..." — happens when you push a new or modified schema to Convex. Here's what the knowledge sources say about it:
What's Happening
When you run npx convex dev or npx convex deploy after adding or modifying a schema, Convex validates that all existing documents in your tables match the new schema. If any documents fail validation, the push will fail. [Schema validation]
How Long Will It Take?
The knowledge sources don't give a specific time estimate, but they do note that the first push after a new index is created (which is similar in nature) is "slightly slower than normal" because Convex has to process each document. For particularly large tables, this backfill/validation process can take longer. [Backfilling indexes]
The duration will depend on how many documents are in your tables.
Does It Cost Money?
The knowledge sources don't explicitly address whether schema validation reads count toward database bandwidth billing. However, given that Convex charges for database reads based on bytes read from the underlying storage, it's possible that validating a large number of documents could incur some bandwidth cost. I cannot confirm this with certainty from the available sources.