OpenMyBot troubleshooting
Locate failures in the daemon, plugins, bindings, permissions and results.
Collect state
Run openmybot status --json, openmybot plugins list --json and openmybot bindings list --json. Record the failed action and IDs. Remove private paths, messages and credentials before sharing diagnostics.
| Error or symptom | Action |
|---|---|
wrok_not_running | Start the daemon and check user/directory |
host_not_bound | Create the host workspace binding |
host_binding_suspended | Inspect scope and reconfirm |
plugin_not_installed | Install the channel plugin and check bundled binaries |
dispatch_queue_full | Wait or cancel unneeded queued work |
operation_conflict | Distinguish a retry from different work under the same ID |
run_not_terminal | Inspect state and wait for completion |
run_not_found | Check ownership by the current binding |
nested_delegation_refused | An OpenMyBot child cannot delegate recursively |
request_timeout | Inspect daemon/run state before retrying |
invalid_arguments | Check absolute paths and supported argument placement |
Follow each stage
Check plugin and credentials for reception, binding and permission for execution, and outbound status for delivery. A live process does not prove the whole journey.
Preserve data
Do not erase the data directory or database to clear an unknown error. Stop normally and follow a recovery procedure for the same version. There is no generally accepted one-click cross-version upgrade/recovery flow yet.