> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/error-codes-table.md). # Error codes table This page lists the error codes returned by the batch file processor. These errors are reported in the output batch file. They can occur while processing the batch file or while executing a specific operation (for example, decrypting the card data). Errors can occur at two levels: * Header level: The error impacts the input file. The level is **H** in the table. * Record level: The error impacts a specific record. The level is **R** in the table. | ERROR CODE | LEVEL | DESCRIPTION | DETAILS | | ---------- | ----- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 100 | H | INVALID\_HEADER | The header in the batch file is not compliant with the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 102 | H | FILE\_TOO\_BIG | The file size exceeds the maximum allowed. | | 103 | H | INVALID\_JSON\_FILE | Check the file [schema](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-json-schema.md). | | 104 | H | NO\_MIGRATION\_RECORDS | No records were found in the processed file. Check the file format and the [schema](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-json-schema.md). | | 105 | H | MANDATORY\_PARAMETER\_MISSING\_HEADER | A required parameter is missing from the header. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 106 | H | FIELD\_INVALID\_FORMAT | A parameter in the file does not match the expected format. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 107 | H | DUPLICATE\_ROW\_ID | Each record must have an incremental `rowId`. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 110 | H | INVALID\_SIGNATURE | Signature verification failed. Check the key used and the [signature computation](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md#signature). | | 111 | H | MISSING\_SIGNATURE | The signature is required. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 112 | H | WRONG\_CONFIGURATION | No configuration was found for the provided `issuerId`. Contact the Thales delivery team. | | 113 | H | UNKNOWN\_ISSUER | The `issuerId` in the batch file does not match any configured issuer. Contact the Thales delivery team. | | 114 | R | CRYPTO\_ERROR | An error occurred while decrypting the record data. Contact the Thales delivery team. | | 115 | R | UNKNOWN CARD PRODUCT | The provided `cardProductId` does not match any configured card product. Contact the Thales delivery team. | | 116 | H | BAD\_FILE\_EXTENSION | The batch file extension is not recognized. Check the [overview](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files.md). | | 117 | H | BAD\_FILE\_NAME | The batch file name is not recognized. Check the [overview](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files.md). | | 130 | H | DUPLICATE\_FILE\_NAME | A batch file with the same name has already been processed. Please ensure batch files are unique. | | 197 | H | UNKNOWN\_OPERATION | The `operation` in the batch file header is not recognized. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 199 | H | PARSING\_ERROR | An unexpected error occurred while parsing the header. Contact the Thales delivery team. | | 201 | R | Incorrect FPAN/Exp format | The card data is not compliant with the expected format. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 202 | R | INVALID\_RECORD | The record is not valid. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 203 | H | MANDATORY\_PARAMETER\_MISSING\_RECORD | A required parameter is missing from the record. Check the [definition](/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/batch-file-structure.md). | | 300 | R | TIG migration token failed | An unexpected error occurred during token migration. Contact the Thales delivery team. | | 900 | R | INTERNAL\_ERROR | An unexpected system error occurred while parsing records. Contact the Thales delivery team. | --- # 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.payments.thalescloud.io/classic-tokenization/use-cases/synchronize-tokens-using-batch-files/error-codes-table.md?ask=&goal= ``` `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.