Troubleshooting
Site Intelligence: Troubleshooting and Recovery
Diagnose and recover common Site Intelligence failures without losing state.
Site Intelligence · Troubleshooting
Connected country, regional, earth-systems, economic, humanitarian, trade, energy, event, alert, scenario, and briefing intelligence.
Purpose
This guide uses an evidence-first diagnostic sequence for Site Intelligence. Preserve state before changing configuration. Determine whether the failure comes from input data, permissions, version identity, browser assets, backend health, schema compatibility, external dependencies, or a product defect.
Prerequisites
- Exact error message and time
- Product, backend, package, and schema versions
- Affected route, feature, record ID, and user role
- A safe backup or export
- The synthetic sample for a reference test
Sample data
This article uses a fictional Resilient Community Retrofit Program. The files contain one demonstration row for every documented feature, so each capability can be tested without private or production data.
Download CSV feature examples · Download JSON workspace example
Preview
| # | Feature | Sample action | Expected result | Classification |
|---|---|---|---|---|
| 1 | Country Dossiers | open a Kenya dossier and inspect update and source metadata | a multi-domain country overview | synthetic-demo |
| 2 | Regional Comparison | compare compatible indicators for Kenya, Tanzania, and Uganda | an aligned table or chart | synthetic-demo |
| 3 | Earth Systems Observatory | review rainfall anomaly, vegetation, weather, and hazard signals | a time-bounded earth-systems view | synthetic-demo |
| 4 | Economics and Markets | inspect inflation, fiscal, food-price, and development indicators | a sourced economic context view | synthetic-demo |
| 5 | Humanitarian and Conflict | review public displacement and humanitarian-need signals | a harm-aware summary | synthetic-demo |
The downloadable files include all 16 feature rows.
Procedure
- Stop repeated imports, submissions, migrations, or destructive retries.
- Record URL, feature, action, role, versions, browser/runtime, and expected result.
- Run the same feature row in a new synthetic workspace.
- If the sample fails, inspect health, logs, browser console, network response, and validation details.
- If the sample succeeds, compare real input schema, units, permissions, size, source, and status with the sample.
- Check version and schema identity before clearing caches or reinstalling.
- Apply the smallest reversible change.
- Repeat the sample and real workflow, then document the result.
Common problems
| Symptom | Likely cause | Safe response |
|---|---|---|
| Data unavailable | provider is delayed, rate-limited, or outside coverage | check status, broaden period, or use a reviewed alternate |
| Version mismatch | WordPress and backend versions differ | align deployments and verify health endpoints |
| Misleading comparison | definition, unit, geography, or period differs | compare only compatible records |
| Live stream empty | filters are too narrow or no event qualifies | expand geography, time, or event type |
Escalation package
- Product and version
- Feature and component
- Exact error text
- Reproduction steps using synthetic data
- Expected and actual result
- Redacted log excerpt without secrets or personal data
- Whether a clean sample reproduces the problem
Expected output
- A reproducible diagnosis or bounded unresolved issue
- Preserved user and system state
- A documented workaround when available
- A support-ready issue summary without private data
Verification
- The synthetic feature succeeds after the fix.
- The original workflow succeeds or remains safely isolated.
- Version and health identity are consistent.
- No duplicates, stale locks, or unintended cache artifacts remain.
- The resolution is reflected in a support article, known issue, or release record when appropriate.
Responsible use
Public intelligence may be incomplete, delayed, or contested; do not use it for targeting, surveillance, emergency command, or unsupported prediction.
Never place credentials, API keys, private URLs, personal records, client documents, or confidential logs in a public article or issue.