Higgsfield shows six different strings when a generation does not come back, and only three of them mean something is wrong with your prompt. The rest are queue state, an unfinished captcha, or a concurrency cap. Getting that mapping right separates a prompt that was fine from a job that was only waiting.

If you are reading this mid-project, a referral link carries up to 50% off for three hours. See the current offer. We may earn a commission through it.

The Six Messages You Actually See

What you seeWhat happenedCredits backDo this
Queued, not movingWaiting for a slotYes, on cancelHover, Cancel, retry
"Something went wrong"Temporary error or skipped captchaYesHard refresh, captcha, retry
"You've hit your limit of generations at the same time"Parallel job cap is fullNothing startedCancel a Queued job or wait
"Rejected due to copyright restrictions" / "IP detected"Copyright check firedYes, in most casesDescribe the look, do not name it
Flagged as NSFWSafety filter firedYes, for most modelsRephrase or swap the reference
Failed, Credits refundedJob failed, refund postedAlready backRetry, then check Usage

Read the third column first. Five of those six are recoverable at zero cost, which is not what red text implies.

The Alarming Ones Are the Free Ones

"Rejected due to copyright restrictions" and "Flagged as NSFW" look like the worst outcomes. They are the cheapest. Both fail fast, both refund automatically for most models, and both are fixable by changing wording or swapping the reference.

The expensive failure is the boring one. A generation that completes is charged even if you hate the output. The error to fear is the absence of an error: the clip that renders clean and is unusable.

Grok is the one model that breaks the refund rule. Its generations are charged the moment they start.

Why Your Prompt Gets Blamed for a Captcha

"Something went wrong" names two causes: a temporary backend error, or a captcha that was never completed. The second is the common one, and it is invisible if you tabbed away mid-submit.

Hard refresh first (Cmd+Shift+R in Chrome, Cmd+Option+R in Safari, Ctrl+Shift+R on Windows), complete the captcha, then retry. A normal refresh reloads the cached bundle and can reproduce the failure.

Cinema Studio adds a second string, "May contain protected content," which is the copyright layer rather than the NSFW filter.

The API Codes Say Something Else

Generate through the API and the language changes.

StatusWhat Higgsfield meansRetry
400Invalid parameters or rejected inputAfter fixing
401Missing or invalid credentialsNo
403Insufficient balanceAfter adding funds
404Request or model not found for that accountNo
409Request still running, for example a delete on a queued jobAfter it finishes
422Validation failed, or an idempotency key reused with different parametersNo
423Model temporarily blockedLater
429Queue full (account_queue_full) or endpoint limit hitAfter Retry-After
500Unexpected server errorYes, with backoff
503Model disabled or not ready, or queue admission unavailableLater, with backoff

Accepted requests can still end as failed or nsfw. Neither is charged.

403 Is Not Forbidden

Every developer reads 403 as a permissions problem and goes hunting for a bad scope. On Higgsfield it means your dollar balance is empty. The key is fine, the request is fine, you are out of money. That mapping eats more debugging hours than any other line in the docs.

Match on status code rather than the human-readable detail string, and send an Idempotency-Key on every submission so a retry after a timeout does not bill twice. Escalate when a job sits Queued past 24 hours or processes past 10 hours, and include the generation ID from the Assets page URL.

The bottom line: five of six messages cost you nothing. Cancel at Queued, complete the captcha, describe the look instead of naming it, and check Usage before you open a ticket.