SP SMMPanelz Docs
Docs/Admin panel/Drip-feed

Drip-feed is one order delivered in scheduled pieces instead of all at once — the way to make a large followers order look natural. Each row here is a drip-feed order and its progress. Live admin: smmpanelz.com/go-admin/dripfeeds.

Reading the screenshots. Blue boxes mark a data value, blue numbered badges mark what you click, client names read as user1 and the amounts are scaled

Page anatomy

Drip-feed page with Active and Completed tabs, search and the drip-feed table
The drip-feed list. State tabs, the search block, then one row per drip-feed order.
#ElementWhat it does
1State tabsAll, Active, Completed and Canceled.
2SearchFinds a drip-feed by Order ID, Link or Username.
3Search fieldChooses which of those the search matches.
4Clear filtersResets the tab and the search.
5RunsDelivered runs out of the total — this is the progress bar of a drip-feed.
6IntervalHow many minutes sit between runs.

Column reference

ColumnMeaning
IDThe drip-feed's own number.
UserThe client who ordered.
AmountWhat the whole drip-feed costs.
LinkThe target being delivered to.
QuantityHow much each run delivers.
ServiceThe service being delivered, as its ID plus its name.
RunsProgress, as done / total. 100/100 means every run has been placed.
IntervalMinutes between runs.
Total quantityThe full amount across all runs — usually runs × quantity.
DateWhen the drip-feed was created.
StatusActive, Completed or Canceled.

How a drip-feed runs

  1. One parent, many child orders. Each run is placed as its own order on the Orders page, tagged Drip-feed next to the client's name.
  2. The panel places them. A background job adds the next run every Interval minutes, so the order keeps delivering while nobody is watching.
  3. Progress is the Runs column. 100/100 is finished; anything short of that still has runs to place.
  4. The money is charged once. The client paid for the whole drip-feed up front, so a failed run is your problem to fix, not a new charge.

To find every child order of one drip-feed, search the client's username on the Orders page and filter Source → Dripfeed. That is the only place the individual runs appear.

On a phone

The dripfeeds page on a phone
Phone view. The Runs column is the progress bar; it is the one thing worth checking on a small screen.

Troubleshooting

A drip-feed stopped part-way

  1. Check whether it is still Active — a drip-feed that looks stuck may simply be waiting out its interval.
  2. Search the client on Orders and look at the last child order's status; if it failed, the drip-feed has nothing to continue from.
  3. Fix the underlying order (provider balance, API key, service limits) — the next run will pick up.

The client says they got everything at once

  1. Check the Interval column. A short interval with a large quantity reads as one delivery.
  2. A drip-feed is configured when the order is placed; changing the pace afterwards means a new drip-feed.

Runs show 100/100 but the total looks short

  1. Compare Runs × Quantity with Total quantity — they should agree.
  2. If they do not, the drip-feed was created with a rounding mismatch; fix the delivery on the child orders with Set partial.