Overview
An account is added, configured, assigned to a device, and does nothing. No follows, no likes, no messages. Nothing in the logs to explain it.
This is the most common support question we receive, and in almost every case the cause is one of six things. This guide walks through them in order, starting with the one that accounts for most of them.
Work through it in order. Each check takes under a minute, and the sequence is deliberate: the cheapest and most likely causes come first. Skipping ahead to the technical checks usually wastes time on a problem that was a single empty field.
The 30-Second Version
- Timer — Start and End must differ.
0to0means the account never runs. - Device — it must be started, not merely connected.
- Login — you log into the app on the phone yourself. Onimator does not do it for you.
- Tool — the tool must be enabled and have sources to work from.
- Limits — the daily cap may already be spent.
- Job Orders — if the work comes from a Job Order, the account must be set to participate.
Start With the Timer
A freshly added account arrives with its Start and End both set to 0. That is not "run all day". It is an empty window, and the bot will refuse to run the account at all.
The app states this plainly:
Required. If Start and End are empty, equal, or invalid, the bot will NOT run this account.
You will also see a red badge reading Start equals End or Invalid schedule.
This single field explains more idle accounts than every other cause combined. It is easy to miss when adding accounts in bulk, because everything else looks correctly configured and nothing errors.
Open the account's settings, go to the Timer tab, and give it a real window. Whole hours (9) or hours and minutes (8:15) both work, on a 24-hour clock. Check the activity bar shows green where you expect, and save.
If the account runs but only sometimes, the window may be narrower than you think, or several accounts may be sharing one device and taking turns. Full detail is in How to Set Up Timers.
Is the Device Actually Running?
A device can be connected and still be doing nothing, because connected and started are two different states.
Is the device started in Onimator? Detection and assignment are not the same as running. Devices must be started before any account on them performs an action.
Is the phone reachable? Onimator talks to the device over ADB. If the cable was moved, the phone rebooted, or USB Debugging was switched off, the connection is gone even though the account still shows as assigned.
Is the phone awake and unlocked? A locked or sleeping device cannot be driven.
Is Onimator running as administrator? Some device operations fail silently without it. See How to Run main.exe and Onimator.exe as Administrator.
Devices, ADB and the 5-step Add Device wizard are covered in What You Need to Start with Onimator.
Is the Account Logged In?
Onimator does not log into the app for you. You install the app on the device and sign in manually, once, before automation can do anything.
This trips up people arriving from browser-based tools, where credentials are entered into the tool itself. Here the tool drives whatever account is already signed into the app on that phone.
Check on the device itself:
The target app is installed on that specific phone
The correct account is signed in
The app opens to a normal feed, not a login screen, a checkpoint, or a "confirm it's you" prompt
A pending verification challenge stops everything. If the app is sitting on a security check, no amount of configuration in Onimator will get past it. Clear it by hand on the device, then let the account settle before running automation again.
Is the Tool Configured?
An enabled tool with nothing to work on produces no actions, and that looks identical to a tool that is switched off.
Is the tool enabled for this account? Settings are per account, not global.
Does it have sources? Follow, Like, Comment and similar tools work from source lists. An empty list means no targets and therefore no actions.
Are the sources still usable? A source list that has been fully processed produces nothing further until you add more. Accounts that worked for weeks and then quietly stopped are usually here.
Are the filters too tight? Country filters, follower thresholds and similar rules can exclude every candidate. If nothing passes the filter, nothing happens.
Post Monitors are a special case. They poll through an integration, and without a key configured they sit on awaiting first poll indefinitely. Enable the integration under Global Settings → Integrations. See Post Monitors.
Has the Account Hit Its Limits?
An account that ran this morning and stopped by lunchtime has probably done exactly what you told it to.
Daily action limits are per account and reset on their own schedule. Once spent, the account goes quiet until the reset.
A block or restriction pauses activity. Check the account's status rather than assuming a configuration fault.
Job Orders participation must be enabled on the account if the work is dispatched that way. An eligible account with participation switched off receives nothing. See What Is the Job Orders Feature.
Global limits, retry policy and recovery behaviour all live in the Global Settings manual.
Common Issues
Everything looks right and it still does nothing. Run Debugger.exe. It surfaces problems the main interface does not show.
It worked yesterday and stopped today. Something changed rather than something being misconfigured. Most likely: the source list ran out, the daily limit was reached, the phone rebooted and lost its connection, or the app logged itself out.
One account on a device works and another does not. That is almost always the Timer. Accounts sharing a device take turns, so check whether the quiet account's window has actually opened yet.
It runs but far slower than expected. Not the same problem. Check delays between actions, the daily cap, and how many accounts are queued on that device.
Nothing at all across every account. Look at the device layer rather than the accounts. One unstarted device or a lost ADB connection affects everything assigned to it.
Safety & Best Practice
Change one thing at a time. Adjusting the timer, the limits and the sources together means you will not know which fixed it, and whether the fix is stable.
Do not raise limits to compensate. If an account is idle because of a configuration fault, increasing the daily cap does nothing while it is broken and pushes it too hard once it is fixed.
Give a recovered account a gentle restart. An account that has been idle or restricted should return at a lower volume for a few days rather than resuming at full pace.
Tutorials & Support
- How to Set Up Timers
- What You Need to Start with Onimator
- How to Use Debugger.exe for Common Issues
- Global Settings Instruction Manual
- How to Report Errors and Bugs to Support
Conclusion
Six checks, in order: timer, device, login, tool configuration, limits, participation. Almost every idle account is explained before the list runs out, and the first one explains most of them.
If you reach the end and the account is still doing nothing, run Debugger.exe and send the output to support. That gives us something concrete to work from rather than a description of silence.