# Downloading Fail Record On Attendee List

When performing bulk importing and also bulk update on the attendee list, organizers will be able to know more regarding the reason of invalid attendee imports. This can be done by downloading the failed record.

## Use Case:

1. When organizer imports a new batch of attendees or bulk updates the current attendee list, there will be an error message that alerts the organizer that there are a certain number of attendees that are invalid.
2. For Bulk Importing Attendees\
   ![](/files/OpEPvfFnkQ5bNetFw540)
3. For Bulk Update\
   ![](/files/7blmKXfRG0LfgcYj39qy)
4. To view the reason that the attendee is invalid, click "Download Fail Record".
5. Once the CSV file is downloaded, scroll to the right to view the column labelled as "failedReason". Organizers will be able to view the reason under this column.\
   ![](/files/DMU1p0tasieqqPrS9TEf)

## List of Failed Reasons

### For Bulk Update:

1. **ATTENDEE\_ID\_INVALID** - Invalid attendee ID
2. **EMAIL\_INVALID**- Invalid email address
3. **UNKNOWN\_FIELD\_ID** - Related to wrong custom field ID in the CSV File header
4. **RADIO\_GROUP\_OPTION\_NOT\_FOUND**- Related to invalid input for single choice field
5. **DROPDOWN\_OPTION\_NOT\_FOUND** - Related to invalid input for dropdown field
6. **CHECKBOX\_GROUP\_OPTION\_NOT\_FOUND**- Related to invalid input for consent text field
7. **TICKET\_CLASS\_NOT\_FOUND**- Related to invalid ticket class name

### For Bulk Import:

1. **EMAIL\_MISSING** - The email field is blank. (Only applies for non in-person events)
2. **EMAIL\_INVALID** - Invalid email address
3. **UNKNOWN\_FIELD\_ID** - Related to wrong custom field ID in the CSV File header
4. **RADIO\_GROUP\_OPTION\_NOT\_FOUND** - Related to invalid input for single choice field
5. **DROPDOWN\_OPTION\_NOT\_FOUND** - Related to invalid input for dropdown field
6. **CHECKBOX\_GROUP\_OPTION\_NOT\_FOUND** - Related to invalid input for consent text field


---

# 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://eventx-hq.gitbook.io/knowledge-base/attendee-management/importing/downloading-fail-record-on-attendee-list.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.