Before you start
System viewing permission is required. Native DG is built in; Odoo is optional.
Steps
- Check each source individually; unconfigured Odoo does not imply native DG failure.
- Read core version, warnings, key expiry, open command counts and oldest pending time.
- Inspect heartbeats and use the background job probe when necessary, then check its response.
Verify the result
Health, worker and probe results should agree. Record non-secret reason codes for failures.
Notes and examples
Odoo key rotation requires operations staff to update configuration and restart. A warning is not completed rotation.
Limitations
Unreachable Odoo, denied access and unsupported version/route require different fixes, not just retries.
Troubleshooting
Check services and network, then bot rights, add-on and key. Observe UNKNOWN commands before rebuilding data.
Frequently asked questions
What is System for?
Inspect order sources, core health, worker heartbeats and background job probes.
What do I need before using System?
System viewing permission is required. Native DG is built in; Odoo is optional.
How do I use System?
Check each source individually; unconfigured Odoo does not imply native DG failure. Read core version, warnings, key expiry, open command counts and oldest pending time. Inspect heartbeats and use the background job probe when necessary, then check its response.
How do I verify the result in System?
Health, worker and probe results should agree. Record non-secret reason codes for failures.
What should I keep in mind in System?
Odoo key rotation requires operations staff to update configuration and restart. A warning is not completed rotation.
What are the limitations of System?
Unreachable Odoo, denied access and unsupported version/route require different fixes, not just retries.
How do I troubleshoot System?
Check services and network, then bot rights, add-on and key. Observe UNKNOWN commands before rebuilding data.