A live settings update is a configuration change that takes effect on a bot that is already running, without stopping and restarting it. In Onimator, settings edited while a bot is active are picked up within seconds and applied to the work still ahead of it. The alternative model, which most automation tooling still uses, requires halting the run, changing the configuration, and starting over, which is a materially more expensive operation than it appears.
Why Restarting Is Expensive
The obvious cost of a restart is lost time. The larger costs are less visible and they are the reason live updates matter operationally.
- Partial rounds are discarded. A bot stopped mid-round loses the progress of that round, and whether the work already done counts toward daily action budgets depends on what the platform recorded, not on what the automation reports.
- Pacing gets disturbed. A stop and restart compresses activity into an unnatural shape, producing a gap followed by a burst. That shape is exactly what behavioral-layer detection looks for, so the restart itself carries risk that the setting change did not.
- Session state is disrupted. Restarting can force app relaunches and re-navigation, and in some cases new logins, each of which is a higher-scrutiny event than the routine actions the bot was performing.
- It scales badly. Restarting one bot is a minor annoyance. Restarting forty across a fleet to apply one threshold change is an operation that people avoid, which means the change does not get made.
That last point is the real one. When configuration changes are expensive, operators stop making them. Settings drift out of date, thresholds stay at whatever was set weeks ago, and the operation runs on stale configuration because correcting it costs more than living with it.
What Live Updates Change Operationally
The practical effect is that configuration becomes a control surface rather than a setup step. Adjustments that were previously deferred to the next natural stopping point can be made immediately:
- Reacting to warning signals. When an account starts producing action blocks or a rising phone verification rate, limits can be reduced immediately rather than after the current run finishes doing the thing that caused the problem.
- Scaling up on a healthy account. Accounts clearing their warm-up cleanly can have their limits raised the moment the evidence supports it, rather than at the next scheduled reconfiguration.
- Correcting mistakes. A misconfigured limit or a wrong source list can be fixed without the run continuing to execute the mistake until it completes.
The shortened feedback loop matters most during warm-up and during recovery, which are precisely the periods when configuration should be changing frequently and when restart cost previously discouraged it.
Scope and Timing
Live updates apply to work the bot has not yet performed. A change does not retroactively alter actions already taken in the current round, and an action already in progress completes under the configuration it started with. The practical timing is that the change is picked up within seconds and governs the work from that point forward.
This has one consequence worth internalizing. Reducing a daily limit below what the account has already done today does not undo those actions. It stops further ones. Operators reacting to a warning signal should understand that the exposure already created is fixed, and the change is preventing additional exposure rather than reversing what happened.
Why It Matters for Automation
Fleet operations are where this compounds. A configuration policy applied across many accounts previously required either a coordinated restart window or accepting that the change rolled out unevenly as each bot happened to stop. Neither is good. The first concentrates all the restart risk into one window, and the second means the fleet runs on mixed configuration for an indeterminate period.
With live updates, a policy change propagates to running bots without any of that. The operational discipline this enables is treating configuration as something reviewed continuously against account health signals, rather than something set during onboarding and revisited only when something breaks.
Live settings update was introduced in Onimator IG Bot v16.1.3.