SMM Order Not Starting? Why Orders Stall and How Automatic Rerouting Works
SMM order not starting? Why orders stall or stop halfway, what start and stall windows are, how rerouting works and how the undelivered part is refunded.
An SMM order not starting is usually stuck at the supplier: a queue, an outage, a link it can't reach, or a line that has quietly stopped. What happens next depends on your panel. At Orbismm, an order that doesn't start within its service's start window is cancelled at the supplier and sent to a backup line automatically.
This guide explains why orders stall, what start and stall windows are, how automatic rerouting to a backup line works step by step, and what happens to the money when an order still can't be finished. For what each status name means, see SMM order statuses explained.
Why do SMM orders stall?
Most panels don't deliver anything themselves. They pass each order to a supplier line, and a line can fail to start, or stop halfway, for reasons that have nothing to do with your order:
| Cause | What you see | What fixes it |
|---|---|---|
| Supplier queue or backlog | Processing for longer than usual | Time, or moving the order to a line with capacity |
| Supplier line down or paused | No movement at all | Moving the order to another line |
| Source stopped working after a platform change | Starts, then stops partway | Moving the rest to another line |
| Private account, deleted post or changed username | No start on any line | Fixing the link; nothing else will help |
| Another order running on the same link | Counts overlap and both look stuck | Letting the first order finish before the next |
| Order near the line's daily capacity | Slow start, slow progress | Smaller orders or drip-feed |
On a panel that relies on a single line per service, every row in that table ends the same way: the order waits until you notice, open a ticket and ask for a cancel.
What are start windows and stall windows?
Each Orbismm service has two time limits, set for that service because a views service and a followers service behave differently:
- Start window: how long an order may wait for delivery to begin. It is about the start time, the gap between placing the order and the first delivered unit.
- Stall window: how long a running order may go without progress before it counts as stalled.
These windows are how the system decides that waiting is no longer reasonable, without anyone watching the order.
How does automatic rerouting to a backup line work?
Every service runs on a primary supplier line with tested backups behind it. When an order misses a window, this is what happens:
- If the order hasn't started within the start window, or stops progressing within the stall window, we cancel it at the supplier.
- The undelivered part goes to the next backup line: automatic rerouting to a backup line. You don't have to ask.
- At most 2 supplier lines receive money for one order.
- Anything that can't be delivered is refunded to your balance automatically, with a ledger entry that says why.
- If a line can't be cancelled, the order is flagged and our team handles it.
Why a cap of 2 lines? Every extra line is another supplier paid for the same order and another chance of two sources delivering to one link. After a second attempt, a clean refund of what's left is better for you than a third try.
How is this different from a panel with one line per service?
| When a line stalls | Single line per service | Primary line with tested backups |
|---|---|---|
| Who notices | You, usually after a client complains | The start or stall window, automatically |
| What happens to the order | It waits on the same line | Cancelled at the supplier, undelivered part moved to a backup |
| What you have to do | Open a ticket and ask for a cancel | Nothing, unless the order is flagged |
| What happens to the money | Refunded when someone processes the ticket | Undelivered part refunded automatically with a ledger entry |
Why panels end up with one line per service, and why the idea of a single main provider doesn't hold up, is covered in our guide to the main SMM provider myth.
A worked example: one order, two lines
For example, with hypothetical numbers: 2,000 followers on a service at $1.40 per 1,000, so the order is charged $2.80 when placed and the price is fixed.
| Step | What happens | Status you see |
|---|---|---|
| 1 | Order placed and sent to the primary line | Processing |
| 2 | The start window passes with no delivery, so the order is cancelled at line 1, which delivered nothing | Processing |
| 3 | All 2,000 go to backup line 2, which starts delivering | In progress |
| 4 | Line 2 delivers 1,700 and stops; the stall window passes and the order is cancelled at line 2 | In progress |
| 5 | The order has now been sent to 2 supplier lines, the cap, so the remaining 300 are not sent to a third line | In progress |
| 6 | The order closes and 300 × $1.40 / 1,000 = $0.42 is refunded to your balance with a ledger entry | Partial |
The order cost you $2.38 for 1,700 followers, and you didn't open a ticket. Through the API, the v2 status action shows Partial with remains at 300, and charge already reflects the refund. With API v1 webhooks, an order.partial event tells your system when it happens.
What should you do while an order hasn't started?
- Open the link in a logged-out browser. If the account is private or the post is gone, no line can deliver to it.
- Compare the wait with the service's median start time over the last 30 days, not with how fast your previous order went.
- Don't place a second order on the same link. On Orbismm, a second order by the same reseller for the same link waits until the first finishes, on services where that matters.
- Check the order log in the panel; moves to a backup line and refunds are recorded there.
- If the order is flagged or you see something that doesn't add up, open a ticket from the order on the support page. People answer 24/7.
How are refunds handled when rerouting can't finish?
Refunds for undelivered parts are automatic and go to your Orbismm balance, with a ledger entry that explains the reason, such as a line stopping after two attempts. The balance can't be withdrawn or transferred; it pays for your next orders. Refunds don't cover drops after delivery; those are handled by refill within the service's window, explained in our guide to what refill covers. The full rules are on the refill and cancel page.
From Orbismm order data
From Orbismm order data: across still being measured orders in the last 30 days, the median start time was still being measured; for the ten most-ordered services it was still being measured.
Check a service's median start time before you order on the [services](/services) page.
Frequently asked questions
- Why is my SMM order not starting?
- Usually the supplier line has a queue or has stopped, or the link is private, deleted or changed. Check the link first, then compare the wait with the service's usual start time.
- What happens if a supplier line goes down mid-order?
- On Orbismm, once the order stops progressing within the service's stall window, it is cancelled at that supplier and the undelivered part moves to a backup line automatically.
- Will my order be sent to a third supplier if the second one fails?
- No. At most 2 supplier lines receive money for one order. Whatever still can't be delivered is refunded to your balance automatically.
- Should I cancel an order that hasn't started and place it again?
- Usually not. Rerouting already moves a stalled order to a backup line, and a second order on the same link makes counts harder to check.
- Do I have to ask for a refund when an order is only partly delivered?
- No. Anything that can't be delivered is refunded to your balance automatically, with a ledger entry that says why.