Processing, Status and Errors
Processing is asynchronous
200 OK means Fusion accepted and queued the report. It does not mean the data reached Corva. Parsing and validation problems never show up in the POST response, so check the report status afterwards. Most reports finish within seconds to a few minutes.
Check status
GET
/integration/report-status/{reportId}Append the path to the base URL for your environment. Use the key the report was posted with: you can only see your own company's reports.
GET /integration/report-status/6a1f0c2e9b3d4e5f6a7b8c9d
Authorization: YOUR_FUSION_API_KEY
{
"status": "success",
"logs": [
{ "date": 1793116800, "step": "integration", "status": "ok" },
{ "date": 1793116801, "step": "report-type-identification", "status": "ok" },
{ "date": 1793116801, "step": "asset-identification", "status": "ok" },
{ "date": 1793116803, "step": "production", "status": "ok" }
]
}
| Status | Meaning | What to do |
|---|---|---|
in-progress | Still processing | Check again later |
success | Data posted to Corva | Nothing |
data-quality / partial-posting | Posted, but some values were flagged or skipped | Review with Corva if it keeps happening |
ignore | Received but intentionally not processed (for example, processing is turned off for that rig) | Contact Corva if you expected it to load |
fail / error and other failure statuses (for example asset not found) | Nothing was posted | See HTTP responses and Troubleshooting |
HTTP responses
| Code | Meaning | Action |
|---|---|---|
| 200 | Accepted (POST) or status returned (GET) | — |
| 400 | Request failed validation (for example missing segment or report_type, or a malformed report ID) | Fix the request. Don't retry it unchanged. |
| 401 / 403 | API key missing, invalid or expired (Access Denied) | Check the header format (raw key, no prefix) and the environment URL |
| 404 | Report not found, or it belongs to another company | Check the report ID and key |
| 500 | Request body is not valid JSON or is larger than 50 MB, or a temporary service problem | Check that the body is valid JSON and under 50 MB. If it is, retry with exponential backoff. |
| 502 / 503 / 504 | Temporary service problem | Retry with exponential backoff |
Updates, resends and backfills
- Updates: resend the record with the same record ID (or the same report date for daily reports). Fusion updates the existing record in Corva instead of duplicating it.
- Ordering: for daily reports, send days in date order. Cumulative values depend on it.
- Backfills: set
"historical": truefor past data. Historical reports go to a separate queue, so live data isn't delayed, and they are not limited to currently active wells. Corva has to enable a historical configuration for your feed first.
Interventions
Don't use historical: true for intervention-segment data unless Corva tells you to.