ResourceExhausted error

[EWinberg]

Hey. I noticed this problem when modules in my header(global partial) and another module in one of my page templates stopped rendering. There has been no changes in the code base for the last couple of moths. I checked the templates in the design manager and was met with this error(One error message per module): 

UnableToExecuteStatementException: java.sql.SQLNonTransientException: Vitess vtgate error: message: "target: Content.-80.primary: vttablet: rpc error: code = ResourceExhausted desc = Out of sort memory, consider increasing server sort buffer size (errno 1038) (sqlstate HY001) (CallerID: contentrenderingapiweb-hubapi-userweb.hs-cosplatform.vitess): Sql: \"select /*+ MAX_EXECUTION_TIME(1503) */ * from module_messages where portal_id = :v1 and `path` = :v2 and deploy_id = :v3 and deleted_at = :vtg1 order by id asc limit :vtg2\\n /* upstream-caller: DesignManagerIde2.77494 */ /* correlation-id: a3b3f436-0851-4a30-ae78-586929501032 */ /* app: contentrenderingapiweb-hubapi-userweb */ /* daoMethod: com.hubspot.designmanager.rendering.customwidgets.ModuleMessageDAO.getByPathAndDeployId(int,java.lang.String,long) */ /* target: Content.primary */ /*vt+ priority: USER *//* user:contentrenderingapiweb-hubapi-userweb.hs-cosplatform.vitess *//* ipAddress: */\", BindVars: {#maxLimit: \"type:INT64 value:\\\"100001\\\"\"v1: \"type:INT64 value:\\\"146084785\\\"\"v2: \"type:VARCHAR value:\\\"/[Theme]/pages/modules/Filterable Resources\\\"\"v3: \"type:INT64 value:\\\"1\\\"\"vtg1: \"type:INT64 value:\\\"0\\\"\"vtg2: \"type:INT64 value:\\\"1000\\\"\"}"code: RESOURCE_EXHAUSTED
[statement:"SELECT /*+ MAX_EXECUTION_TIME(1503) */ * FROM module_messages
WHERE portal_id = :portal_id AND path = :path AND deploy_id = :deploy_id AND deleted_at = 0
ORDER BY id
LIMIT 1000
", arguments:{positional:{0:146084785,1:/[Theme]/pages/modules/Filterable Resources,2:1}, named:{path:/[Theme]/pages/modules/Filterable Resources,portal_id:[PortalId],deploy_id:1}, finder:[]}]

From what I could find online, this error appears when a modules revision history makes the sort memory overflow. The only fix I could find was to clone each "faulty" module and recreate/replace them in the cms pages. This doesn't seem like a sustainable solution to me. So my questions are: Why does this error occur? and is there a more reasonable fix than to recreate all of my content?

Any help is appreciated!

[RubenBurdin]

Hi @EWinberg  @JErling   yep, this one really looks like a HubSpot-side incident rather than anything you “broke” in your theme.

That Vitess RESOURCE_EXHAUSTED / “Out of sort memory” error is coming from HubSpot’s backend when the Design Manager tries to fetch module_messages and sort them. Even if the message mentions a specific module path, the fact you’re seeing it across templates and even across themes is a strong signal it’s not about one bad module revision history on your end, but a platform regression or capacity issue in the content rendering pipeline.

In 2025, when you hit errors like this inside the Design Manager (saving files suddenly fails, modules stop rendering, no recent code changes), the most reliable “fix” is exactly what you both did: open a Support ticket. Support can escalate to the product team and apply whatever backend cleanup or patch is needed. Cloning modules or rebuilding content might appear to help sometimes, but it’s not a sustainable remedy if the underlying query or infrastructure is the real culprit.

For anyone landing here later, a couple practical notes. Grab a correlation id from the error (you’ve got one in the stack trace) and include it in the Support ticket. Mention that it happens across multiple assets and themes, and that it blocks saves in Design Manager. That makes it easier for HubSpot to find the failing query and link it to any known incident or deployed fix.

Sounds like HubSpot already shipped a fix on Dec 10 in at least one wave, so if anyone still sees it after that, Support is the right channel to get your portal reprocessed. Hope this helps others avoid wasting hours on workarounds.

[EWinberg]

I got a  slightly cryptic response from HubSpot today, declaring that it was an error on their side! Problem's now solved

[JErling]

I am having the exact same issue. I was editing my theme files and they were saving just fine, then suddenly every section and template file had this error start to show on them about an hour ago. This is also happening up across my entire account, regardless of whether I am working on a completely different theme or not.

I reached out to support, hopefully it will get resolved quickly becuase it has put a hard stop on any work I can do.

[BérangèreL]

Hi @JErling, thank you so much for getting back to us!
 

I noticed the Support ticket you opened, and I wanted to share the resolution here so it can help other Community Members who might face something similar.
 

Great news! Our product team let us know that a fix was deployed for this issue on December 10th, and everything should now be working smoothly.
 

You should be all set now!
 

Thank you again, and wishing you a wonderful day! 🌞
Bérangère

[EWinberg]

Somehow it feels reassuring that we're not alone in this! I got a response from the Hubspot technicql support saying that it probably was an issue with templates using requests in an inefficient manner. Doesn't really clear things up in my case but if you get a clearer answer could you post it here for future reference, and for the poor people in the same boat as us!

[JErling]

Support was able to resolve the issue pretty quickly and I was able to start saving my changes again. Everything was working properly again about 4 hours after I reached out to support.

I was worried becuase there was not much else I could do but wait, considering that this is something that happened on the HubSpot backend, but for anyone in the same boat, reach out to support and explain the issue, they will get you back up and running as fast as possible.

[BérangèreL · Accepted solution]

Hi @EWinberg and welcome, it's a pleasure to have you here! 🤗

Thanks for reaching out to the HubSpot Community!

The error suggests the module's revision history has grown too large. HubSpot Support should be able to investigate this for you. I'd recommend that you get in touch with the HubSpot Support.

Let's consult our Top Experts as they might have seen this type of error: Hi @d-lupo, @tmcginnis and @Anton do you have any insights to share to help @EWinberg, please?

Thanks so much and have a great day!
Bérangère