Hmm… if you’re referring to HuggingChat Omni, I wonder if the October 30 fix might be relevant:
There was a temporary fix for a live HuggingChat production problem on October 30, 2026. A maintainer reported that some DeepSeek Flash requests were routed to a provider that rejected the configured output-token limit. The temporary configuration change was merged that day, with successful tests reported for the adjusted setting.
It might be related, but it doesn’t establish what happened to your two failing projects. We don’t yet know whether you’re using HuggingChat Omni, which models are involved, or whether the error is still happening. That same message can appear for different reasons, including a failed inference request, an issue with a particular conversation, or a problem in another application.
The lowest-effort route I’d suggest:
I wouldn’t top up again, delete the original work, reset a Space, or change a spending limit just to see whether the message goes away. The fact that two work and two don’t is already a useful starting point.
The optional sections below give the possible branches and sources in more detail; none requires you to carry out every check.
A small, safe comparison if the problem continues The two most helpful details would be whether the error still occurs and what you mean by the four “projects.” If a model name or safely redacted error code is already available, that may narrow it further, but there’s no need for another payment or a lengthy debugging session just to reply.