Skip to content
Lumean API

Descriptions are in English

The section interface is translated into your language, but descriptions of operations, schemas and errors exist only in Russian and English — the English version is shown here.

policy_cooldown_active — cooldown after policy blocks

429policy_cooldown_activeRetry-After present

What happened

The fifth 429 source, and the only "order-side" one that has Retry-After: the body additionally includes retry_after (seconds) and retry_at (ISO-8601). Creation of new orders is suspended entirely, not just for the disputed text.

Why

Five consecutive tasks blocked by policy trigger a 5-minute pause; repeat offenses raise it to 10, then 15 minutes (the step does not go any higher). Only content blocks count: infrastructure failures (worker timeout, network) do not move the counter.

What to do right now

The pause only helps on paper. If you send the same text after the cooldown, it will be blocked again, the counter starts over, and the step goes up — the fix is editing the text, not waiting. Any successfully completed task resets both the counter and the step reached.

Which request to send next

After retry_at — POST /orders with the CORRECTED text. Queueing the very same text is the fastest way to reach the 15-minute step.

Feed this page to an AI

Open .mdllm.md

spec 0.0.1