Jamf Import Set Fails to Process Staging Records After Data LoadIssue Jamf schedule job executes successfully, loading data into staging tables, but the imported records remain unprocessed in CMDB tables, with import sets remaining in "pending" or "did not complete" states. Symptoms Import sets for Jamf data are stuck in "pending" or "did not complete" states.Transform Map triggers do not occur automatically after data is loaded into staging tables.Manual intervention (clicking "Transform Map" under Related Links) is required to process records. Error: com.snc.cobject.IllegalFieldNameException: Invalid field name: [*] Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 2.14.4 Cause A specific entity mapping created during ETL loading caused validation failures during transformation. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When we load the integrationHub ETL for the first time for any ETL definition, some temp entities will get created as part of schema load based on the import set selected in step 1 Creation of required temp entities are expected and is explained in the below article: https://www.servicenow.com/community/cmdb-forum/ih-etl-faq-ih-etl-auto-recreate-temp-entity-after-changing/m-p/3534327/thread-id/20550#M20551 Sample entities created when SG-JAMF computer ETL was loaded: temp.software.available_updates[*] temp.software.plugins[*] When some temp entities gets validated during transform and cause transformation failure. To fix it, we can this to ignore-true in the entity mapping table so it doesn't get validated and cause transformation failures.