Troubleshooting
Find rapid solutions to common errors, execution bottlenecks, network timeouts, and tool permission issues encountered in Plannix Bot workspaces.
Common error codes
| Error Code | Meaning | Resolution |
|---|---|---|
ERR_SANDBOX_TIMEOUT | Container boot exceeded 60s | Verify container image availability or pre-warm worker nodes. |
ERR_TOOL_APPROVAL_DENIED | Action rejected by operator | Review workspace approval policies under Manage and protect. |
ERR_NETWORK_UNREACHABLE | Egress connection blocked | Verify corporate forward proxy configuration and DNS resolvers. |
ERR_OOM_EXIT_137 | Process killed by Linux OOM | Increase container compute profile from Standard (4GB) to Build (32GB). |
Container startup and network timeouts
If containers fail to establish WebSocket streaming, ensure your corporate firewall allows outbound TCP connections on port 443 to *.plannix.web.id and does not drop long-lived HTTP upgrade handshakes.
Permission denied on tools
When running bash scripts, bots execute under a non-root unprivileged user (sandbox-user). If a script requires root, use our pre-approved passwordless sudo capabilities or request admin elevation via approval cards.
Out of memory (OOM) failures
Language compilers (such as Rust or TypeScript) and large Node.js builds can exceed default RAM limits. Pass memory allocation flags or select a higher compute tier:
# Increase Node.js memory limit inside task
export NODE_OPTIONS="--max-old-space-size=8192"
npm run buildRunning CLI diagnostic commands
Run plannix-bot doctor from your local terminal to verify authentication, network routes, latency, and sandbox compatibility:
plannix-bot doctor
[OK] Authentication: Valid (token expires in 28 days)
[OK] Cloud API Gateway: 32ms latency
[OK] WebSocket Protocol: Connected
[OK] Local Docker Bridge: Ready