> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/deploy/setup/production-setup/deploy-complaints-management/unified-approach-not-for-publish/fixing-errors.md).

# Fixing Errors

## Understanding Error Messages

If something goes wrong, the system shows an error file.

![](/files/PPWOnfeRpeau6IBAflDK)

### Opening the Error File

Download and open the error Excel file.

![](/files/WL1AFBser8voFlnYyLT5)

### Reading Error Columns

The file has three extra columns at the end:

| Column           | What it Means                        |
| ---------------- | ------------------------------------ |
| \_STATUS         | SUCCESS, EXISTS, or FAILED           |
| \_STATUS\_CODE   | Number code (201=success, 400=error) |
| \_ERROR\_MESSAGE | What went wrong                      |

#### Common Errors and Solutions

Error: "Department not found"

Solution: Check the department name spelling. It must match exactly.

***

Error: "Mobile number already exists"

Solution: This mobile number is already used. Enter a different number.

***

Error: "Invalid date format"

Solution: Use DD-MM-YYYY format (e.g., 01-01-2024)

***

Error: "Parent code not found"

Solution: The parent boundary does not exist. Check the parent code.

***

## Steps To Fix and Re-upload

Step 1: Open the error file

Step 2: Find rows with FAILED status

Step 3: Fix the errors in those rows

Step 4: Save the file

Step 5: Upload again to the notebook of the specific phase 

***

## Quick Tips

#### Tip 1: Always Save Before Upload

Save your Excel file before uploading to avoid losing work.

#### Tip 2: Don't Change Column Names

Never rename or delete column headers in templates.

#### Tip 3: Check Spelling

Department names, codes, and references must match exactly.

#### Tip 4: One Phase at a Time

Complete each phase before moving to the next.

#### Tip 5: Keep Templates Safe

Save copies of your filled templates for future reference.

***

## Getting Help

#### If You Are Stuck

1. Check this guide again
2. Look at the error message carefully
3. Contact your IT support team

***

## Checklist

Use this checklist to track your progress:

#### Setup

* [x] Jupyter Notebook is open
* [x] DataLoader.ipynb is open
* [x] I have my login credentials

#### Phase 0: Login

* [x] Entered gateway URL
* [x] Entered username and password
* [x] Login successful ✅

#### Phase 1: Tenant & Branding

* [x] Downloaded template
* [x] Filled Tenant Info sheet
* [x] Filled Branding Details sheet
* [x] Uploaded and processed ✅

#### Phase 2: Boundaries

* [x] Created/selected hierarchy
* [x] Generated template
* [x] Filled boundary data
* [x] Uploaded and processed ✅

#### Phase 3: Common Masters

* [x] Downloaded template
* [x] Filled Departments & Designations
* [x] Filled Complaint Types
* [x] Uploaded and processed ✅

#### Phase 4: Employees

* [x] Generated dynamic template
* [x] Filled Employee Master
* [x] Uploaded and processed ✅

#### Final Check

* [x] All phases completed
* [x] No errors remaining
* [x] Data verified in the CRS application


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.digit.org/complaints-management/deploy/setup/production-setup/deploy-complaints-management/unified-approach-not-for-publish/fixing-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.