---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Glossary import error scenarios

# Glossary import error scenarios {#ariaid-title1}

Release version: Australia  
Updated January 23, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Glossary import error scenarios

This document outlines the various error and warning messages ServiceNow customers may encounter when uploading glossary term files.
It explains how these issues affect the import process and whether the import can proceed successfully.
Understanding these scenarios helps customers troubleshoot import failures and optimize data uploads.
Show full answer Show less  

## File-level errors

File-level errors prevent the entire glossary import from succeeding. Common issues include:

* Unsupported file format (only XLSX allowed)
* File size exceeding limits
* More rows than permitted in one file
* Invalid file structure
* System errors during file processing

When these errors occur, the import is blocked and must be corrected before retrying.

## Row-level errors

Row-level errors affect individual rows, causing those rows to be skipped, while allowing other valid rows to import. Examples include:

* Missing required Title field for new or existing rows
* Records not found or inaccessible due to permissions

## Row-level warnings

Warnings indicate non-critical issues where specific fields or values are skipped or modified, but the row still imports. These include:

* Nonexistent domains, owners, or tags (fields skipped or invalid tags ignored)
* Invalid status values (field skipped)
* Duplicate titles (row imported as duplicate)
* Overly long values truncated automatically
* Attempts to change system-managed fields (original value retained)

## Commit-time errors

These errors occur during the final save process and may cause partial failures:

* Record modified by another user after preview generation
* System errors preventing record updates

Rows with commit-time errors fail individually while others may succeed.

## Final import status

After processing, the system reports one of three statuses to indicate import success level:

* **COMMITTED** --- All rows imported successfully
* **PARTIAL** --- Some rows imported; others failed
* **FAILED** --- No rows imported

Being aware of these error types and their impact enables customers to effectively diagnose and resolve import issues, ensuring glossary data is uploaded accurately and efficiently.  
Error and warning messages that can occur when uploading glossary term files, and their impact on the import process.
An error state indicates that the file cannot be uploaded without fixing the issue. A warning state means the specific field or value with the warning is skipped, but the rest of your data imports successfully.

## File-level errors {#glossary-import-error-scenarios__file-level-errors}

{#glossary-import-error-scenarios__file-level-errors__entry__3}

| Scenario | Type | Will import succeed? |
|-|-|-|
| The file format is incorrect. Only XLSX files are supported. | Error | NO |
| The file size exceeds the maximum allowed limit. | Error | NO |
| The file contains more rows than allowed. Consider splitting your upload into smaller files. | Error | NO |
| The file structure is invalid. | Error | NO |
| A system error occurred while processing your file. | Error | NO |
[Table 1. File-level error scenarios]

## Row-level errors {#glossary-import-error-scenarios__row-level-errors}

{#glossary-import-error-scenarios__row-level-errors__entry__3}

| Scenario | Type | Will import succeed? |
|-|-|-|
| The required Title field is empty for a new row. | Error | Partial --- row is skipped |
| The Title field has been removed from an existing row. Title is required. | Error | Partial --- row is skipped |
| The record cannot be found or you don't have permission to access it. | Error | Partial --- row is skipped |
[Table 2. Row-level error scenarios]

## Row-level warnings {#glossary-import-error-scenarios__row-level-warnings}

{#glossary-import-error-scenarios__row-level-warnings__entry__3}

| Scenario | Type | Will import succeed? |
|-|-|-|
| The domain does not exist in the system. | Warning | YES --- domain field is skipped |
| The owner email does not match any user in the system. | Warning | YES --- owner field is skipped |
| The status value is not valid for this field. | Warning | YES --- status field is skipped |
| One or more tag names do not exist in the system. | Warning | YES --- invalid tags are skipped; valid tags are applied |
| The title already exists in the system. | Warning | YES --- row imports as a duplicate |
| A field value is too long and will be automatically shortened. | Warning | YES --- value is truncated and applied |
| You attempted to change a system-managed field. The original value is retained. | Warning | YES --- field is unchanged |
[Table 3. Row-level warning scenarios]

## Commit-time errors {#glossary-import-error-scenarios__commit-time-errors}

{#glossary-import-error-scenarios__commit-time-errors__entry__3}

| Scenario | Type | Will import succeed? |
|-|-|-|
| The record was modified by another user after your preview was generated. | Error | Partial --- row fails; others may succeed |
| The record could not be updated due to a system error. | Error | Partial --- row fails; others may succeed |
[Table 4. Commit-time error scenarios]

## Final import status {#glossary-import-error-scenarios__import-status}

After the import completes, the system displays one of the following status values:

* COMMITTED --- All rows imported successfully
* PARTIAL --- Some rows imported; others failed
* FAILED --- No rows imported