The Queue#
Every generation command goes into a single shared queue. This page explains how your place in it is decided, how many jobs you can have waiting, and what the bot does and does not tell you while you wait.
One job at a time, first in first out#
Two rules cover almost everything:
- Exactly one job runs at a time. Eimi runs on one GPU in the maintainer's home, and that GPU is not shared between jobs. When your job starts, it has the machine to itself until it finishes.
- The queue is strict first-in, first-out by submission time. The oldest waiting job is always the next one to run. There is no shuffling, no weighting, and no round-robin between users.
That means the wait you see is simply everything submitted before you, run back to back. How long that takes on any given day depends on what else is running on that one machine, so treat wait times as a rough shape rather than a number you can plan around.
The two exceptions both put a job back where it already was, not ahead of anyone new:
| Exception | Why |
|---|---|
| A job that failed and is being retried automatically | It goes back to the front so it resumes where it was in line rather than starting over at the back. See Failures. |
| A job that was already running when the bot restarted | It is re-attached at the front so tracking can resume mid-generation. |
That second row comes up more than you might expect. This is a home setup, not a datacentre: the bot restarts fairly often, the machine gets rebooted, and sometimes the whole thing is just off for a while. A queue that stops moving, or a card that vanishes after a restart, is normal for a bot like this rather than something going wrong.
There are no priority tiers#
This is the single most common misconception, so plainly:
Admins and VIPs do not skip the line
There is no priority queue, no fast lane, and no boost that moves your job forward. An admin who submits after you waits behind you. A VIP who submits after you waits behind you. Server boosters get nothing special in the queue at all.
What the higher tiers actually buy:
| Tier | What it changes |
|---|---|
| VIP | A higher cap on how many jobs you can have queued at once, more GPU power for your jobs, and access to VIP-only models |
| Admin | The same kind of caps, plus admin jobs are hidden from the bot's public status counter |
| Booster | Nothing queue-related |
See Access and tiers for who gets what.
How many jobs you can queue#
Your limit counts everything of yours that is waiting plus currently running.
| Limit | Value |
|---|---|
| Global queue capacity, all users combined | 95 jobs |
| Per user | 15 jobs |
| Per VIP user | 15 jobs |
| Per-channel or per-server caps | None configured |
If you are at your limit, the command is rejected immediately with a private message:
Job Limit Reached
You have 15 job(s) in the queue.
Your limit is 15. Please wait for a job to complete.
Nothing is queued and nothing is lost -- run the command again once one of your jobs finishes.
If the whole queue is full at 95 jobs, your card is replaced with
❌ Failed to add job to queue. and an alert is raised for the admins.
Note
Because there is exactly one execution slot, a queue full of jobs from one person and a queue full of jobs from fifteen people behave identically. The cap is there to stop one person filling all 95 slots, not to give anyone a turn sooner.
Your queue position is not shown#
Eimi does not display your position in line. A waiting job shows 🕒 Queued and nothing
else -- no number, no "3rd in queue", no place marker. Do not go looking for one, it is not
hidden somewhere on the card.
The same applies to per-job time estimates: there is no ETA on a job card, at any stage.
Where the estimate does show up#
Eimi's own Discord presence -- the status line under the bot's name in the member list -- is the one place queue information is published. It updates every 5 seconds.
| State | Presence |
|---|---|
| Nothing queued | Online, Listening to your imagination |
| Jobs queued or running | Idle, Watching 3 imagine · 2 edit · ~5 min |
The breakdown counts jobs by type, sorted by count, joined with ·. Job types that can
appear are imagine, turbo, edit, upscale, usdu, compose, nano and gpt. The
time is the estimated total for everything currently in the queue: ~N min above a minute,
otherwise ~N sec rounded to the nearest 5.
Note
Admin jobs are not counted in this display. If the presence says the queue is empty but a job is clearly running, an admin submitted it.
How the estimate is produced#
Eimi learns from its own history rather than guessing:
- Every successful job records how long it took, filed under a key made from the model, batch size, LoRAs, steps, CFG, resolution and GPU power level.
- The estimate for a new job is the rolling average of the last 100 similar jobs. Samples under 5 seconds are discarded as cache hits.
- If no exact match exists, it falls back to the same model with a different LoRA set, scaling by batch size, then to a per-model default.
- For the job that is currently running, the historical figure is blended with the backend's own live estimate at 75% historical, 25% backend for stability.
- The queue total is that running job's remaining time plus a full estimate for every job behind it.
The first few runs of a new model or an unusual setting will be the least accurate, since there is no history to average yet.
When results are spaced out#
If two jobs finish back to back in the same channel, Eimi waits at least 1.5 seconds between posting the results, so Discord does not rate limit the channel. A short pause before your image appears is expected, not a fault.
Lockdown#
Admins can put Eimi into lockdown, which stops the queue from starting anything new. Jobs are still accepted normally, they simply never run.
Lockdown gives you no message at all
There is no maintenance notice, no banner, and no reply telling you the bot is paused.
From your side lockdown looks exactly like a queue that has stopped moving: your card
sits on 🕒 Queued indefinitely, and so does everyone else's.
If a job never starts and the bot is otherwise responding to commands, ask an admin whether lockdown is on before you resubmit. Resubmitting only consumes more of your 15-job allowance.
Related#
- Progress cards -- what the card shows once your job starts
- Failures -- retries, timeouts, and what happens on a restart
/imagine-- the main command that feeds the queue