# 6. Fix Errors

## Overview

Uploads can fail due to validation errors. Most phases are safe to re-run after you fix the input.

### 6.1 Start with the cell output

Check the last executed cell output. Look for:

* HTTP status codes (`400`, `401`, `403`, `500`)
* “Failed: X” counts
* Row-level validation messages

### 6.2 Use the processed error sheet (when generated)

Some uploads generate a processed error sheet. It usually contains:

* The failing row
* A reason column
* A suggested fix

Fix the rows. Upload again.

### 6.3 Re-run strategy

Prefer this loop:

1. Fix the data in the template.
2. Upload the corrected file.
3. Re-run the same processing cell.

If the notebook says the call is **idempotent**, re-running is expected.

### 6.4 When you need deeper help

Use the full guide in [Error Handling](/complaints-management/complaints-resolution-v2.10/deploy/setup/production-setup/deploy-complaints-management/error-handling.md).

<details>

<summary><strong>Rollbacks</strong></summary>

Rollback steps are environment-specific. Documentation is being added. For production, plan rollbacks via database and object-store backups.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.digit.org/complaints-management/complaints-resolution-v2.10/deploy/setup/production-setup/deploy-complaints-management/unified-approach/6.-fix-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.