Ideogram Concurrency and Queue Control

Ideogram Concurrency and Queue Control

Overview

Keep paid image work inside a measurable concurrency envelope. Combine admission control, tenant fairness, operation deadlines, and endpoint-aware retry so a traffic burst does not become duplicate spend, an unbounded queue, or persistent 429 pressure.

Prerequisites

• Request arrival rate, latency objective, output count, endpoint mix, and cost ceiling.
• Queue ownership, per-tenant policy, cancellation behavior, and overload response.
• Current account capacity and an approved contact path for increased scale.

Current Contract

Ideogram's API overview documents a default limit of 10 in-flight requests and directs larger-capacity needs to [email protected]. This is a concurrency boundary, not permission to launch ten workers per process. Account-wide observed behavior remains authoritative.

Authentication

Workers inject IDEOGRAM_API_KEY server-side and send Api-Key only to https://api.ideogram.ai. Queue records and metrics must exclude keys, prompts, images, and response URLs.

Instructions

1. Measure arrival rate, service time by endpoint, current in-flight count, queue age, timeout rate, and 429 responses.
2. Place a shared account-level semaphore below the verified limit; start conservatively and reserve capacity for recovery probes.
3. Add bounded per-tenant admission, queue length, age, output count, and total operation deadlines.
4. Prefer asynchronous endpoints for work that cannot fit an interactive deadline and persist each generation_id.
5. Retry only classified transient responses using server guidance when present, exponential backoff with jitter, and a strict attempt ceiling.
6. Prevent ambiguous duplicate generation by reconciling known async identifiers before resubmission.
7. Raise capacity only through the vendor path and a reviewed load plan; canary the new limit.

Tool Discipline

Use Read, Glob, and Grep for queue, worker, metric, and fixture inspection. Use Write and Edit for approved limit, test, or documentation changes. Invocation does not authorize load generation, quota negotiation, or increased production concurrency.

Approval Boundaries

Require owners for live load tests, spend, tenant-priority changes, queue dropping, capacity increases, and deployment. Document how queued work is cancelled or drained before changing the envelope.

Error Handling