Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
403 Access Denied | Wrong key or header format, or the key is for another environment | Send the raw key with no prefix, to the URL for your environment |
405 / HTML response | Posting to the Fusion website instead of the API, or missing /integration | Use the exact URL from Endpoints and Authentication |
Status fail, asset not found | No Corva well matched your identifiers | Send API/UWI and wellbore name; ask Corva to add alternative well names. See Well Identification. |
| Data on the wrong wellbore | Wellbore name missing or different from Corva | Send wellbore_name exactly as it appears in Corva |
| Report type not identified | No mapping configured for that report type for your company | Ask Corva to enable it. Your payload may be fine. |
| Duplicate records | Record IDs change between resends | Send stable record IDs |
500 right after posting | Malformed JSON or a payload over 50 MB | Validate the JSON and split the payload; retry only after that |
502 / 503 / 504 | Temporary service problem | Retry with backoff |
Get help
Contact your Corva integration contact or the Corva support portal. Include the Fusion report ID with every question.