Log Files
Log files present problems and errors that occur during the Migration process and are available in the Workflow Progress Table.
Form Submission Errors
To aid in troubleshooting, when a form fails, Vault provides the error type and the reason. This information is only available for the most common “actionable” errors:
- OPEN_CIRCUIT_BREAKER
- BAD_GATEWAY
- CONNECTION_ERROR
- UNKNOWN ERROR
Error types are included in the Post-Run log file and the Migrations Report. The log file contains detailed information on form submission failures, such as specific rules or subject IDs. The Failed_Skipped_Task_Types report in the Migrations Report provides the failure’s error type only. For example, if a log file provides the following error record:
BAD_GATEWAY - Trusted API responded with a retriable error
The Migrations Report will only provide the error type, which is BAD_GATEWAY.
Reviewing Form Submission Errors
When an error occurs, data is generated in the Post-Run log file after the completion of the Post-Run step.
Click Log File in the Post-Run row of the Workflow Progress section to download the log file. Successful form submissions will generate an empty log file.
If further attempts are retried and successful, the previous error records are still present in the log file for troubleshooting purposes. The maximum error record count is 100 per run type-error type combination.
Med Coding Errors
Failures occurring during the Med Coding step are indicated by an error icon in the Workflow Progress section.
Click Log File in the Med Coding row of the Workflow Progress section to download the log file and view the error type and message. Successful Med Coding runs generate an empty log file.
The only error type and message for Med Coding is Lock Timeout > LOCK_TIMEOUT. If further attempts are retried and successful, the previous error records are still present in the log file for troubleshooting purposes. The maximum error record count is 100 per error type.
Retrying Steps
When a step is retried and a log file is available, the old log file is replaced by the new one.
Log Messages, Errors & Warnings
The table in this section lists log file messages, such as errors, and warnings to aid in resolving load failure.
Column Definitions
Use the following definitions to better understand the table:
- Code Name: The unique system identifier for the log entry as it appears in the log file.
- Phase: The phase of the Validate & Stage workflow where the activity occurs.
- Message Type: The log severity classification:
- Error: Severe
- Warning: Moderate
- Info: Low severity, informational
- Requires Aggregation?: How the system groups repetitive issues:
- No: The log file will show every instance of the issue.
- Yes: The log file will show the first 50 instances of the issue.
- Message: The exact message as it appears in the log file. The placeholders ‘%s’ and ‘%d’ represent text and numbers, such as file names.
Log Message Table
| Code Name | Phase | Message Type | Requires Aggregation? | Message |
|---|---|---|---|---|
UNEXPECTED_ERROR |
Pre-process | Error | No | An unexpected exception occurred during the %s execution. Error message is '%s' |
YAML_READ_ERROR |
Pre-process | Error | No | Error reading YAML file '%s'. Error Message is '%s' |
YAML_FILE_PARSE_ERROR |
Pre-process | Error | No | Failed to parse YAML file '%s'. Error Message is '%s' |
CSV_FILE_OPEN_ERROR |
Pre-process | Error | No | Error opening file '%s'. Error message is '%s'. Cause of error is '%s' |
LOAD_STOPPED |
Pre-process | Error | No | Error opening file '%s'. Error message is '%s' |
TRANSFORMERS_YAML_FILE_OPEN_FAILED |
Pre-process | Error | No | Error opening file '%s'. Error message is '%s'. No default transformers can be applied |
TRANSFORMERS_YAML_FILE_PARSE_FAILED |
Pre-process | Error | No | Failed to parse YAML file '%s'. Error Message is '%s'. No default transformers can be applied |
CUSTOM_ERROR |
Pre-process | Error | No | %s' |
FAILED_TO_APPLY_TRANSFORMATION |
Transform | Error | Yes | Applying the transformation for %s resulted in an exception. Skipping this %s from migrating to CDMS. |
SKIPPING_CSV_SITEParsing |
Parsing | Info | Yes | Skipping CSV site as it is only defined in Source Data CSV but not defined in 'Load Sites' Error Message: %s |
DATA_HANDLER_BUILD_FAILED_FOR_CSV |
Parsing | Error | No | Exception while trying to build data handlers to parse data from CSV file. Error message is '%s' |
DATA_PARSING_FAILED_FOR_CSV |
Parsing | Error | No | Exception while trying to parse data from CSV file. Error message is '%s' |
ADD_STUDY_ID_SITE_MISSING |
Study ID | Error | Yes | Site name in the data not found in the Study |
ADD_STUDY_ID_LOAD_MISSING_INFO |
Study ID | Error | Yes | Load Details are Missing: %s must be included in Load Details |
ITEM_VALIDATION_UNEXPECTED_ERROR |
Data Validation | Error | Yes | Item validation: Unexpected error %s |
ITEM_VALIDATION_LENGTH |
Data Validation | Error | Yes | Item validation: Item value exceeds allowed length of %d |
ITEM_VALIDATION_MAX_LENGTH |
Data Validation | Error | Yes | Item validation: Item value exceeds max allowed length of 1500 |
ITEM_VALIDATION_NUMERIC |
Data Validation | Error | Yes | Item validation: Item value is non-numeric |
ITEM_VALIDATION_PRECISION |
Data Validation | Error | Yes | Item validation: Item value precision greater than allowed precision of %d |
ITEM_CODELIST_ITEM |
Data Validation | Error | Yes | Item validation: Codelist item not found in Codelist %s |
ITEM_UNIT_ITEM |
Data Validation | Error | Yes | Item validation: Unit value not found in unit definition %s |
ITEM_UNIT_VALUE_SOURCE_DATA_MISSING |
Data Validation | Error | Yes | Item validation: Unit value exists in source data but item value is missing |
ITEM_UNIT_VALUE_REQUIRED |
Data Validation | Error | Yes | Item validation: A unit value is required when an item value is provided |
ITEM_LAB_CODELIST_ITEM |
Data Validation | Error | No | Item validation: Lab Codelist item not found in Lab Codelist '%s'. Ensure the value exists and is not archived. |
ITEM_LAB_UNIT_ITEM |
Data Validation | Error | No | Item validation: Lab Unit item not found in Lab Unit '%s'. Ensure the value exists and is not archived. |
ITEM_LAB_MODIFIER |
Data Validation | Error | No | Item validation: Lab Modifier not found. Ensure the value exists and is not archived. |
ITEM_LAB_MODIFIER_DISABLED |
Data Validation | Error | No | Item validation: Lab Modifier not enabled for '%s' analyte |
ITEM_LAB_VALUE_ITEM_VALUE |
Data Validation | Error | No | Item validation: Lab co-dependency missing, either lab value or item value is missing. |
ITEM_LAB_LOCATION |
Data Validation | Error | No | Item validation: There was no match found for Lab ID %s. |
ITEM_CLINICAL_SIGNIFICANCE |
Data Validation | Error | No | Item validation: '%s' does not match any Clinical Significance value. |
EMPTY_LAB_LOCATION_NOT_ILB |
Data Validation | Error | No | Lab Location' for Form '%s' cannot be empty unless the location or its Form is also ILB in attributes.csv. |
ITEM_CODELIST_UNEXPECTED_ERROR |
Data Validation | Error | Yes | Item validation: Codelist size is not 1 |
ITEM_UNIT_UNEXPECTED_ERROR |
Data Validation | Error | Yes | Item validation: Unit not found in item definition %s |
ITEM_LAB_CODELIST_UNEXPECTED_ERROR |
Data Validation | Error | No | Item validation: Lab Codelist size is not 1 |
ITEM_LAB_UNIT_UNEXPECTED_ERROR |
Data Validation | Error | No | Item validation: Lab Unit size is not 1 |
ITEM_BOOLEAN |
Data Validation | Error | Yes | Item validation: Boolean is not 'true' or 'false' |
DATE_PARSE_ERROR |
Data Validation | Error | Yes | %s validation: Unable to parse date. %s |
ITEM_DATE_FREE_DATE_ERROR |
Data Validation | Error | Yes | Item validation: problem with unknown date |
ITEM_DATE_MORE_SPECIFIC_NOT_FREE_ERROR |
Data Validation | Error | Yes | Item validation: more specific date part should also be unknown |
ITEM_TIME_PARSE_ERROR |
Data Validation | Error | Yes | Item validation: Unable to parse time |
ITEM_LAB_TIME_MISSING |
Data Validation | Error | No | Item validation: Time missing from 'Collection Date Time.' |
ITEM_TIME_FREE_TIME_ERROR |
Data Validation | Error | Yes | Item validation: problem with unknown time |
ITEM_TIME_MORE_SPECIFIC_NOT_FREE_ERROR |
Data Validation | Error | Yes | Item validation: more specific time part should also be unknown |
UNKNOWN_TIME_ERROR |
Data Validation | Error | Yes | Item validation: Time is present when item is 'Always Unknown.' |
FORM_VALIDATION_INVALID_FORM_STATUS |
Data Validation | Error | Yes | Form validation: Invalid form status %s |
ELEMENT_DEFINITION_MISSING_IN_STUDY_DESIGN_ERROR |
Data Validation | Error | Yes | Validation: Incorrect identity %s |
SOURCE_DATA_TARGETING_INCORRECT_IDENTITY_ERROR |
Data Validation | Error | Yes | Validation: Incorrect identity %s |
INCORRECT_VALUE_ERROR |
Data Validation | Error | Yes | Validation: Incorrect value %s |
BLANK_CODING_ITEM |
Data Validation | Error | No | Source data contains blank items for med coding. You must supply a verbatim value for these items. |
RELATED_OBJECT_DEFINITION_MISSING_IN_STUDY_DESIGN_ERROR |
Data Validation | Error | Yes | Validation: %s not configured in the study design |
RELATED_OBJECT_DEFINITION_CONFIGURED_IN_STUDY_ERROR |
Data Validation | Error | Yes | Validation: %s configured in the study when it should not be |
LOG_EVENT_HAS_VISIT_METHOD |
Data Validation | Error | Yes | LOG Events cannot have Visit Methods. |
VISIT_METHOD_IMPROPER_VALUE |
Data Validation | Error | Yes | %s is not a valid Visit Method value. |
VISIT_METHOD_IMPROPER_VALUE_STUDY_DESIGN |
Data Validation | Error | Yes | %s is not a valid Visit Method value for this event. |
VISIT_METHOD_REQUIRED |
Data Validation | Error | Yes | Visit Method is required by Study Design but is not provided. |
EXECUTION_ATTR_TARGET_LOG_EVENT_SUBTYPE |
Data Validation | Error | Yes | Field %s cannot be frozen or locked on LOG event. |
FORM_LINK_NO_LINKS_CSV |
Data Validation | Warning | Yes | This study has form links. A links.csv is required. |
ITEM_LINK_NO_LINKS_CSV |
Data Validation | Warning | Yes | This study has item links. A links.csv is required. |
HEADER_COLUMN_MAPPING_ERROR |
YAML Validation | Error | Yes | Header mapping of %s does not match any column name in the csv |
NO_COLUMN_DEFINED |
YAML Validation | Warning | Yes | No column name defined for %s |
MATCHING_COLUMN_MISSING_IN_CSV |
YAML Validation | Warning | Yes | No column name matching %s defined for %s found in csv |
MISSING_COMPONENT |
YAML Validation | Warning | Yes | No component named %s defined for %s |
NO_MAP_DEFINED |
YAML Validation | Warning | Yes | No map defined for %s |
NO_MAP_DEFINED_WITH_PARENT_CONTEXT |
YAML Validation | Warning | Yes | No map defined for %s with parent %s |
NO_CHILD_ELEMENTS |
YAML Validation | Warning | Yes | No %s defined for %s |
NO_VEEVADEF_DEFINED |
YAML Validation | Warning | Yes | No veevaDef defined for %s |
ELEMENT_NOT_FOUND_IN_STUDY_DESIGN |
YAML Validation | Error | Yes | Element %s matching veevaDef %s not found in the study |
ELEMENT_HIERARCHY_NOT_MATCHING_STUDY_DESIGN |
YAML Validation | Warning | Yes | %s relation not found in study design. |
ELEMENT_REPEATING_NOT_MATCHING_STUDY_DESIGN |
YAML Validation | Warning | Yes | %s is set to repeating equal to %s in study but not in yaml |
NO_VISIT_DATE_DEFINED |
YAML Validation | Warning | Yes | No visit date defined for event %s |
VISIT_DATE_FORMAT_INCORRECT |
YAML Validation | Error | Yes | Event visit date format must match TAPI expected format ISO_LOCAL_DATE (yyyy-mm-dd) |
ITEM_UNIT_VALUE_MAPPING_MISSING |
YAML Validation | Error | Yes | Item validation: Unit value mapping missing from yaml |
ITEM_UNIT_VALUE_INVALID_TYPE |
YAML Validation | Error | Yes | Item validation: Unit value applied to non-unit item |
DUPLICATE_ELEMENT |
YAML Validation | Warning | Yes | Duplicate %s with veevaDef %s defined under %s |
MISMATCHED_CSV |
YAML Validation | Warning | Yes | CSV file name %s defined in yaml does not match csv file %s assigned to load |
STUDY_DESIGN_RETRIEVAL_ERROR |
YAML Validation | Error | Yes | Error getting %s with veevaDef=%s from study design |
MEDICAL_CODING_ITEM_DEFINITION_STATE_ERROR |
YAML Validation | Error | Yes | Medical Coding Item Definition must exist and be active for forms that have coded items |
SETTING_DATA_IN_RESTRICTED_FORM |
YAML Validation | Warning | Yes | Warning: Data is being mapped to a restricted form |
EXCLUDING_STATIC_ELEMENT |
YAML Validation | Error | Yes | Error: Static/Required element %s is targeted for exclusion |
DERIVED_COLUMN_NAME_ERROR |
YAML Validation | Error | Yes | At least one derived column name matches a column name in the csv |
INVALID_REFERENCE |
YAML Validation | Error | Yes | Invalid identity reference used in %s |
DUPLICATE_REFERENCE |
YAML Validation | Warning | Yes | Configured identities are not uniquely named in %s |
INVALID_FORM_EXCLUSION |
YAML Validation | Error | Yes | Invalid form exclusion: %s |
INVALID_HEADER_EXCLUSION |
YAML Validation | Error | Yes | Invalid header exclusion: %s |
DUPLICATE_RECORD_DETECTED |
YAML Validation | Warning | No | Some Items found in this data were already registered. |
DERIVED_ITEM_MAPPED |
YAML Validation | Error | No | You can't directly apply attributes to a derived item. Please fix the attributes.csv |
INVALID_ILB_ITEM |
YAML Validation | Error | No | attributes.csv: You cannot directly ILB '%s.' |
POST_STAGE_VALIDATE_REPEATING_ABOVE_MAX |
Post Staging | Error | Yes | Repeating count exceed max allowed in study |
POST_STAGE_VALIDATE_REPEATING_NOT_ALLOWED |
Post Staging | Error | Yes | Repeating not allowed in study |
POST_STAGE_VALIDATE_ATTRIBUTE_STRUCTURE |
Post Staging | Error | Yes | Attribute record targets both parent and child |
POST_STAGE_VALIDATE_INVALID_LAB_ITEM |
Post Staging | Error | No | %s' are calculated by the system. They should not be included in the YAML. |
POST_STAGE_VALIDATE_LAB_HEADER_ITEM_MISSING |
Post Staging | Error | No | %s' missing from source YAML. |
POST_STAGE_VALIDATE_ATTRIBUTE_MISSING_TARGET |
Post Staging | Error | Yes | Object directly targeted in attributes.csv doesn't exist in source data. |
POST_STAGE_INVALID_ILB_ATTRIBUTE |
Post Staging | Warning | Yes | Cannot ILB target that has item(s) with value supplied in source data |
POST_STAGE_VALIDATE_QUERY_MISSING_TARGET |
Post Staging | Error | Yes | Query record missing directly targeting object |
POST_STAGE_VALIDATE_QUERY_MESSAGE_SEQUENCE |
Post Staging | Error | Yes | Query Message Sequence does not match Message Date Sequence |
POST_STAGE_VALIDATE_QUERY_MESSAGE_SEQUENCE_STARTING_INDEX |
Post Staging | Error | Yes | Query Message Sequence must start at 1 for each unique query id |
POST_STAGE_VALIDATE_EMPTY_QUERY |
Post Staging | Error | Yes | Query has no messages attached |
POST_STAGE_VALIDATE_FIRST_QUERY_MESSAGE_NOT_OPEN |
Post Staging | Error | Yes | Query's first message is not 'Open' |
POST_STAGE_VALIDATE_CONSECUTIVE_ANSWERED_MESSAGES |
Post Staging | Error | Yes | Answered Query Message has an answered message before it |
POST_STAGE_VALIDATE_CLOSED_NOT_REOPENED |
Post Staging | Error | Yes | Closed Query Message can only be followed by an Open message |
POST_STAGE_VALIDATE_FORM_LINK_MISSING_TARGET |
Post Staging | Error | Yes | Link record missing directly targeting object |
POST_STAGE_UNMATCHED_NCD |
Post Staging | Warning | No | Non-clinical data was not matched to a YAML |
POST_STAGE_INVALIDATE_ATTRIBUTE |
Post Staging | Warning | Yes | %s - Attribute not applied because the object's ancestor or descendant was created by repair. |
POST_STAGE_INVALIDATE_SIG_EVENT_WITH_OPEN_QUERY |
Post Staging | Warning | Yes | Signature Attribute not applied because the event has an open query on event date. |
POST_STAGE_INVALIDATE_SIG_FORM_WITH_OPEN_QUERY |
Post Staging | Warning | Yes | Signature Attribute not applied because the form's descendant contains an open query. |
POST_STAGE_INVALID_FORM_LINK |
Post Staging | Warning | Yes | The links.csv contains a form-to-form or item-to-form link that does not exist in the study design. The form link won't be created until the study design is updated. |