Where is your Swarmbot automation? Check the Device Wall status and logs
Swarmbot shows an automation task's status on the relevant Device Wall card and lets you open its logs and result. For teams managing several phones, this is a quick way to identify which device needs attention before checking the actual on-device outcome.
Swarmbot shows automation progress on the card for each affected phone in the Device Wall. If you manage several work or test phones, select the devices, start a saved task, and open its “Logs / Results” from the card. The status helps you see where to look next; a successful task status is not, by itself, proof that every business step inside an app produced the intended outcome.
Start from the Device Wall
- Check the device numbers, labels, and connection state. Select only the phones involved in this run. If you need help defining the selection, see the Device Wall selection guide.
- Choose “Run Task” in the bottom action area, select a locally saved script or quick instruction, and review its devices and parameters before starting. For an unfamiliar workflow, begin with a small selection.
- Watch the status on each relevant device card. Open “Logs / Results” on a card when you need details about that task. With multiple phones, review each result rather than assuming that one card represents the entire selection.
The card can indicate queued, running, stopping, succeeded, failed, or cancelled. A “syncing” message means Swarmbot is retrieving the latest task state; it does not establish that execution failed. After a task finishes, you can dismiss its card overlay. Dismissing the overlay or closing the log panel does not erase the execution record or stop a task that is still running. For older runs, use Developer → Execution Records.
What should you verify after a success status?
Task logs tell you what Swarmbot recorded about execution. If the script was meant to install or open an app, or complete a workflow within it, inspect the target phone or the resulting business record as well. On failure, identify the affected device and the specific step in its logs, check connectivity and prerequisites, and then decide whether a retry is safe. Avoid rerunning steps that may have already produced a non-repeatable effect. See the automation failure guide for a fuller troubleshooting path.
This workflow is useful once you have a saved task and want to follow its progress without leaving the Device Wall. This guide reflects the current public stable release and its interface documentation; check the official release information for the available version.