Job error log
This page lists common issues that can occur during subscription jobs. Learn about the errors, warnings, and informational messages, and discover how to resolve them.
Error messages
| Code | Explanation | How to Resolve |
|---|---|---|
| E0002 | An internal runtime error occurred. | Create a support ticket with the error details. |
| E0024 | An attempt was made to update a DCR that has already been processed (accepted or rejected). | Remove the DCR from your DCR import file as it has already been updated/processed. |
| E0025 | A child record could not be processed because its master key is null and the DCR ID referenced does not exist in the DCR import file. | Ensure all child records in the DCR import file have a valid, non-null master key and that the referenced DCR ID is present and correctly formatted in the same import file. |
| E0026 | The DCR result value in the DCR response file is invalid. | Ensure the DCR result is either 'CHANGE_ACCEPTED' or 'CHANGE_REJECTED'. For details of the DCR response file, see About the DCR import file. |
| E0027 | The checkbox 'DCR Response File Provided' is enabled on the subscription, but no DCR response file was found in the inbound folder. | If the 'DCR Response File Provided' checkbox is enabled, ensure a DCR response file is present in the inbound folder. For details, see Load the DCR response. |
| E0028 | The format of the master key (primary key of the third-party master) provided in the DCR response file is incomplete or invalid. |
Ensure the master key in the DCR response file includes all three parts:
|
| E0029 | The DCR response file is missing the master key (primary key of the third-party master). | If the DCR result is 'CHANGE_ACCEPTED', the master key must be included in the DCR response file. It is not required for 'CHANGE_REJECTED' results. |
| E0030 | The DCR response file included a master key for which no matching record exists in the data feed. | Ensure every master key in the DCR response file has a matching record with the same master key in the third-party master source files. The blue record needs to be updated within the same job to update the DCR. |
| E0031 | The DCR response file does not contain any DCRs to process. | Ensure at least one update to an unprocessed DCR is included in your DCR response file. |
| E0034 | An error occurred while parsing the SQL of your transformation query due to incorrect syntax or references to non-existent columns or tables/files. | Ensure your SQL query follows correct syntax and references existing columns and tables/files. Test your query in the SQL Query Editor. |
| E0038 | An attempt was made to export a Network ID which is a merge loser (record state = 'MERGED_INTO'). | Determine the merge winner Network ID and use that Network ID in your export list. |
| E0039 | An attempt was made to reference a sub-object (for example, address or parent HCO) using an unknown Network ID. | Ensure the Network ID provided for the sub-object in the source file is correct and exists in your Network MDM instance. |
| E0043 | A user manually stopped the job. | If you did not initiate the cancellation, contact the user who canceled the job to determine the reason. |
| E0045 | The job was stopped because another job of the same type is already running. The subscription that you attempted to run only allows one job to run at a time. |
Wait for the existing job to complete, or check system activity for stuck jobs. |
| E0047 | A job trigger could not be started because the referenced job or user was not found. | Review your job triggers to ensure all referenced jobs or user accounts exist and are active. |
| E0049 | The job trigger was interrupted and automatically paused following an unexpected restart of internal application services. | Check if the job remains stalled, cancel the job and restart it manually. If the job cannot be restarted or fails again, please submit a Veeva Support ticket. |
| E0050 | The job ended due to a waiting timeout, indicating it took too long to complete a specific operation. | Review the job configurations. Consider re-running the job with a smaller data volume. If the issue still occurs create a support ticket. |
| E0055 | Number of matches found exceeds limit of 20000000. | Review and refine your match rules to prevent over-matching. |
| E0060 | The data feed provided a blank or null value for an attribute that is explictly configured to not allow blank/null values. | Ensure the field is populated with a value in the source file. |
| E0063 | An update was attempted on a child record with a state that does not allow updates (for example, 'MERGED_INTO' or 'UNDER_REVIEW'). | If the record state is 'UNDER_REVIEW', wait for data change request completion. If 'MERGED_INTO', apply updates to the merge winner record. |
| E0076 | The entity types of the records you are attempting to merge do not match (for example, merging an HCP with an HCO). | Ensure the records you are trying to merge have identical entity types. |
| E0083 | The format of the custom key provided in the source feed is incomplete or invalid. |
Ensure the custom key in the source feed includes all three parts:
|
| E0085 | An attempt was made to update a record with an alternate key value that is already used by another record. | An alternate key value cannot be added to a record if it is already used by another record. Either use a different alternate key value for your update or remove the existing alternate key value from the other record. |
| E0087 | An unknown reference code was provided for a picklist field (reference type). | Add the reference code to the field's reference type, use reference aliases, or enable auto-adding new reference codes. |
| E0091 | An attempt was made to change an existing alternate key. By default, a field that already has an alternate key value cannot be overridden. | If you are confident that you want to override existing alternate key values, add this advanced job property to your source subscription: "job.merge.overrideAlternateIdentifier": "true". Keep in mind that changes to existing key values can have an impact on consuming downstream systems. |
| E0093 | An attempt was made to update a third-party mastered record without providing the external master key. | Ensure the external master key is included in the source feed and correctly mapped in the model map. |
| E0095 | An update was attempted on a record with a state that does not allow updates (for example, 'MERGED_INTO' or 'UNDER_REVIEW'). | If the record state is 'UNDER_REVIEW', wait for data change request completion. If 'MERGED_INTO', apply updates to the merge winner record. |
| E0096 | A custom key provided for this record already exists on another record. Custom keys must be unique; there cannot be two or more records that share the same custom key. |
Review custom key mappings and check source data for duplicate custom keys. Consider enabling source deduplication if duplicates are included in the source feed. |
| E0097 | An attempt was made to merge or unmerge records. The merge/unmerge failed because the resulting custom keys conflict with an existing active custom key. |
Review the custom keys on the records you're merging/unmerging. Use Reporting to identify other records already using those keys. You can then either inactivate the conflicting existing custom keys or re-evaluate your merge/unmerge strategy. |
| E0098 | You've reached the maximum limit for reporting individual duplicate custom key errors. This means more than 500 entities were rejected due to custom key conflicts, but they were not individually logged. | A high number of collisions suggests a general issue with your subscription. Review your input data and custom key configuration to identify the root cause of the duplicate custom keys. Correct the underlying issue in your data or key mapping logic, and then re-run the subscription. |
| E0101 | A general error occurred during a merge extension, potentially related to custom logic. | Create a support ticket with the error details. |
| E0102 | The record provided in the source file contains an invalid Network ID. | Ensure the Network ID in the source file is valid and correctly formatted. |
| E0107 | One or more rows in your source file could not be parsed because the number of columns did not match the header row. | Check affected row(s) in your source file. Unescaped delimiters within a field value can impact column parsing. Verify text qualifiers and field delimiters are correctly set. |
| E0108 | Lines in the source file were skipped during parsing due to errors or malformations. | Review the source file for malformed lines or data. |
| E0109 | An general error occurred during a function call, likely related to a Network Expression Rules (NEX) function. | Review the Network Expression Rules on data model fields or the subscription. If further assistance is needed, create a support ticket with the error details. |
| E0110 | Reference aliases are defined for your subscription's source system, but the reference code in the source file did not match any defined alias. | Ensure all reference codes provided in your source file have a defined reference alias. |
| E0111 | An attempt was made to update a third-party master record from a different source than its creator. Only the source system that created the third-party master record can make updates. |
Check the record owner and ensure your source subscription uses the correct source system for updates. |
| E0112 | The master key provided in the DCR import file does not match the Network ID in the system, causing a mismatch during processing. | Verify that the master key in your DCR import file maps to the right Network ID. Ensure the master key is not already assigned to a different record in the Network MDM instance. |
Warnings
| Code | Details | Action |
|---|---|---|
| W0002 | An internal runtime error occurred | Create a support ticket with the error details. |
| W0012 |
When HCPs are anonymized, Network MDM automatically closes all associated pending tasks, such as Data Change Requests (DCRs) or Suspect Match tasks.
Although the record anonymization process was successful, one or more related tasks could not be closed automatically by the job. |
Use Network Reporting to generate a list of pending tasks linked to the recently anonymized HCPs. Review each identified task and manually close or resolve it to ensure data consistency. |
| W0014 | An attempt was made to anonymize a record that is not in a 'DELETED' state. Only deleted records can be anonymized. |
For OpenData or third-party-managed records, unsubscribe the record before anonymization. For locally managed records, soft-delete the record before anonymization. |
| W0016 | The record update was rejected due to a job validation rule violation. | Review the job validation rule conditions (System Interfaces > Job Validation Rules). Compare them against the data you're trying to load. To resolve the issue, ensure your data complies with the rule. If you're confident the update should proceed, you can temporarily disable the rule to allow the data to be accepted. |
| W0018 | Either the inbound FTP folder contains no new files, or no entities could be parsed/modeled from the source files. |
Ensure new source files are present in the inbound folder.
Also, double-check the following:
|
| W0021 | The record was not grouped for matching with any other records. | Review data grouping criteria to ensure all incoming records can be grouped for matching. |
| W0022 | An attempt was made to match on an invalid Network ID. | Check your source file to ensure the column(s) mapped to the 'vid__v' field(s) contain valid Network IDs. |
| W0023 | An attempt was made to match two master records (OpenData or third-party master records). | Ensure you are only matching 'grey' records to 'orange/blue' records, or 'grey' to 'grey' records. |
| W0026 | A data group's size exceeded the limit of 1000 records. Records beyond this limit are excluded from matching. | Review your data grouping criteria to ensure each data group remains below the 1000-record limit. |
| W0028 | The match request (Match against master) could not be directed to an OpenData instance because the provided country code is invalid or lacks an OpenData subscription for the country. | Ensure the provided country code is valid and has an active OpenData subscription. |
| W0030 | The record you are trying to merge into has record state 'DELETED'. You cannot merge into deleted records. | Review the records you are trying to merge. Identify the merge winner record for the merge loser and use it as your merge target. |
| W0031 | An attempt was made to merge or update a record that is in a 'DELETED' state. You cannot merge or update a record which is deleted already. |
Remove deleted records from your source feed. |
| W0047 | A relationship could not be created because the related record either wasn't provided in the data feed or doesn't exist in your Network MDM instance. | Ensure the related record is provided within the same data feed or already exists in your Network MDM instance. |
| W0048 | An attempt was made to merge records. That merge request failed because the target record of the merge specified by the source key could not be found in your Network MDM instance. | Ensure the target record of the merge exists in the system, is not being filtered out, and has successfully loaded without errors in the current or previous jobs. |
| W0050 | Some foreign keys in the sub-object file (for example. address) do not have a matching ID in the source file containing the main object (for example,HCP or HCO). | Ensure that for every foreign key in the sub-object file, there is a matching record in the main object file. |
| W0051 | An attempt was made to load 4-byte characters into Network MDM, which were not supported before release 25R1.1. | In release 25R1.1 or higher, 4-byte characters are supported. Re-run your subscription if necessary. |
| W0052 | The Network Address Inheritance refresh job did not detect any addresses that required a re-sync. | All your addresses are in sync. There is no issue to troubleshoot. |
| W0054 | Lines in the source file were skipped during parsing due to errors or malformations. | Review the source file for malformed lines or data. |
| W0056 | An attempt was made to soft-delete a record that is not locally managed (gray). Only locally managed records can be soft-deleted. |
Remove all OpenData or third-party mastered records from your soft-deletion list to ensure only locally managed (gray) records are processed. |
| W0059 | An attempt was made to unsubscribe a mastered record (OpenData or third-party) with a state other than 'VALID'. Only valid records can be unsubscribed. | Check the record state of the record you are trying to unsubscribe. If 'DELETED', it means the record has already been unsubscribed. |
| W0060 | An attempt was made to unsubscribe a record that is not externally mastered by OpenData or a third-party master. | Remove the affected Network ID from your unsubscribe job. |
| W0061 | A general error occurred during a merge extension, potentially related to custom logic. | Create a support ticket with the error details. |
| W0062 | A general error occurred during a merge extension, potentially related to custom logic. | Create a support ticket with the error details. |
| W0063 | A row is missing a value for the mandatory REFERENCE_TYPE column, making it impossible to categorize the record. | Populate the REFERENCE_TYPE field for the specified line in your source file to ensure the code is mapped to the correct category. |
| W0064 | The unique identifier for a reference code (COD_ID_ONEKEY) is missing for the specified reference type. | Provide the missing code value in the source file. Every reference entry must have a unique ID to be processed by Network MDM. |
| W0065 | The mandatory PROCESS column (instruction) is empty, so the system does not know whether to add/update or delete the code. | Add the appropriate instruction to the PROCESS column (for example, "R" for Replace/Update or "D" for Delete). |
| W0066 | The value provided in the PROCESS column is not supported. Only "R" (Replace) and "D" (Delete) are recognized. | Correct the instruction value in the source file to either "R" or "D" as required. |
| W0067 | The reference code entry is missing a language code (LANGUAGE_CD) for its label. | Ensure a valid ISO language code (for example, "EN", "FR") is provided in the LANGUAGE_CD column for the specified line. |
| W0068 | The language code provided in the LANGUAGE_CD column is not supported or recognized by the system. | Verify and correct the language code to a supported standard format. Ensure the language is supported in Network. |
| W0069 | The mandatory start date for the reference code's validity (COD_BEG_VAL_DATE) is missing. | Populate the COD_BEG_VAL_DATE column in your source file with a valid start date. |
| W0070 | The value provided for the begin-valid date is not a recognized date format (YYYY-MM-DD). | Correct the date in the COD_BEG_VAL_DATE column to match the expected format (YYYY-MM-DD). |
| W0071 | The reference code entry is missing an end-valid date (COD_END_VAL_DATE). | Provide a valid end date in the source file. For codes that do not expire, use a far-future date or the standard system default. |
| W0072 | The value provided for the end-valid date is incorrectly formatted or contains invalid characters. | Verify and correct the date format in the COD_END_VAL_DATE column of your source file. |
| W0073 | The descriptive label for the reference code (COD_LONG_LBL) is missing. | Provide a descriptive label in the COD_LONG_LBL column to ensure the reference code is identifiable in the UI. |
| W0074 | Multiple rows for the same reference code were found with contradictory instructions (for example, one row says Delete, another says Replace). | Review the source file for duplicate entries of the same reference code. Ensure the PROCESS instruction is consistent across all rows for that code. |
| W0075 | An unknown reference code was provided for a picklist field (reference type). | Add the reference code to the field's reference type, use reference aliases, or enable auto-adding new reference codes. |
Informational messages
| Code | Details | Action |
|---|---|---|
| I0013 | An attempt was made to change the value of the primary_country__v field. |
The primary_country__v field cannot be changed after record creation. When updating an existing record, provide a primary country identical to the current field value. |
| I0016 | Your instance's data was temporarily out of sync with the OpenData master instance, but has now been updated to be in sync again. | This is an informational message; the data sync issue should be resolved. If you observe further errors on your OpenData subscription or during a download, submit a support ticket. |
Contact Veeva Support
If the issue does not have a documented error code, or you are unable to resolve the issue using the error details, contact Veeva Support for assistance.