Once an order is placed, StreamBoost tracks it until it genuinely finishes. This article covers what each state means, what moves an order between them, and the two cases people most often misread: partial delivery and provider outages.
The states
| State | Meaning |
|---|---|
| Queued | Accepted. Fulfilment has not started yet. |
| In progress | Being fulfilled. Delivered count may be well below target. |
| Partially delivered | Some quantity has arrived and the order is not finished. Where continuation is supported, StreamBoost keeps pursuing the rest. |
| Completed | The full requested quantity was delivered. |
| Cancelled | Stopped deliberately. The record is kept. |
| Failed | Could not be fulfilled. |
Only Completed, Cancelled and Failed are final. Everything else is an order that is still being worked on.
Partially delivered is not finished
This is the one worth reading twice. An order showing *Partially delivered — continuing* at 37 of 100 has 63 units still owed. StreamBoost has not given up on it, has not marked it terminal, and has not refunded it. It is still working.
Whether a partial order can be continued depends on the system fulfilling it. Where continuation is supported, StreamBoost asks it to continue the existing job on every cycle until the target is reached. It never creates a second job to top up the first — that would be ordering the same work twice.
How progress actually reaches you
A background worker runs on the server, on its own schedule, independent of anyone's browser. Each cycle it checks the health of each fulfilment system, then reads the status of every order that is not finished and records what came back.
When something changes, your open order page is updated over a live connection — no refresh, no polling from your browser to anything external. Your browser talks to StreamBoost and only to StreamBoost. If that live connection cannot be established, the page falls back to refreshing itself periodically so it still stays honest.
- Progress only comes from fulfilment. Nothing in your browser can advance it.
- Delivered is clamped to what you ordered. Over-reporting cannot invent units.
- Closing the tab changes nothing. Tracking is server-side.
When fulfilment goes down
An unreachable fulfilment system says something about that system, not about your order. StreamBoost does not fail your order, does not cancel it and does not refund it — the work may well be happening and simply not reportable at that moment.
What changes is only how often StreamBoost asks. Retries back off on a fixed ladder — 30 seconds, 1 minute, 2 minutes, 5 minutes, then 10 minutes, where it holds — and any success resets that ladder immediately, so one blip does not leave an order on a slow schedule for the rest of its life.
While this is happening your order shows Waiting for provider. It keeps its progress and resumes automatically once delivery is available again.
Whether order processing is degraded right now:
Check current statusWhen an order is cancelled
Cancellation is final. The order stops being checked, stops being continued, and stops occupying the work queue immediately — but the record stays exactly where it was.
You keep the order id, the target, the quantity requested, the quantity delivered, the price and the full timeline. Cancelling ends processing; it does not erase history, which is what keeps your billing record auditable afterwards.
When to ask for help
Some services deliver in bursts rather than steadily, so a flat period is normal and not a fault. If an order has been genuinely stalled far longer than that service usually takes, open a ticket with the order reference and it can be looked at directly.
The Help Center covers the common cases; a ticket covers yours:
Contact support