Understand repeat runs, new-post subscriptions and the checks that prevent the wrong quantity or target.
Drip-feed repeats delivery to the same target across several runs. A subscription watches a specified profile and creates orders for posts that match its settings. These are different jobs: use the first to schedule a defined target, and consider the second only when you need an ongoing new-post workflow. Availability depends on the selected service. A service name containing “automatic” is not enough; read the fields and description before deciding which workflow it represents.
Check the quantity per run, number of runs, interval and total charge before submitting a drip-feed order. Use the units shown beside each field.
For example, if the form specifies 100 units per run and 5 runs, the total is 500 units. Confirm that the quantity field really means “per run” and that the interval uses the unit you intended.
Check the requested username format, minimum and maximum quantity, number of future posts, any old-post option, delay and expiry. Leaving a field blank can behave differently from entering zero, so follow the service instructions rather than experimenting with a live purchase. Keep a record of which profile is covered and review its subscription status when names or posting patterns change. Make sure the account has the funds needed for the workflow shown by the panel.
After starting a schedule, inspect the order and subscription records to confirm the correct target and quantities. If nothing appears, check the subscription status, target requirements and remaining funds before creating another schedule. Pause or stop through the available controls when the original purpose ends. Timing changes do not establish account safety, prevent removals or guarantee organic distribution. Treat pacing as an operational setting and keep its results separate from your content-performance conclusions.