Environment Troubleshooting
Use this guide when environments go offline, fail to sync, or run workflows unreliably.
Fast Triage
- Is the environment online?
- Is the agent/container running?
- Can host reach platform API endpoint?
- Are credentials valid and unexpired?
- Are system resources exhausted?
Symptom-Based Diagnosis
Environment stuck offline
Likely causes:
- agent not running
- network path blocked
- invalid token
Sync not updating
Likely causes:
- API reachability issues
- sync interval misconfigured
- server-side auth rejection
Executions failing after deploy
Likely causes:
- missing model or dependency
- datasource unavailable from target network
- config mismatch in workflow nodes
Runtime Commands (Typical)
docker ps
docker logs solutionengine-agent --tail 200
Use environment and workflow logs together to correlate failures.
Preventive Controls
- monitor heartbeat and error trends
- apply controlled rollout for major changes
- test dependency reachability from the target host
- keep rollback workflow versions ready