The fleet does not come back after a power cut
If the controlling software runs in a console window, a reboot or power cut takes the fleet offline until a human opens it again. It has to be registered as a system service that starts automatically and restarts on failure.
How to isolate it
1. Register as a service
The controlling agent must start at boot without a logged in user, and restart automatically if it exits.
2. Make the kernel service automatic
The service that talks to the control chips also has to start on boot, before the agent tries to connect.
3. Test by actually rebooting
Pull the power and walk away. If the fleet is posting again without intervention, it passes. If not, it does not.
4. Add an offline alert
The fleet should tell you it is down rather than you discovering it in the morning numbers.
5. Consider hosting instead
If reboot survivability on your own premises is the problem, a hosted fleet removes it entirely.
Let us build your fleet.
Tell us how many creators you run and how you get traffic today. We will show you the system running on a real fleet and tell you honestly which setup fits, or whether it fits at all. Every build is scoped and quoted around your agency.
Message us on WhatsApp Telegram