Loading import set table with error: <staging table>: no thrown error

[Hetang Modi]

In one of the integrations, I am getting the following message - "Loading import set table with error: <my_import_set_table>: no thrown error" logged at Error level. My question is, if there is no thrown error, is it an error? Moreover, how do I get details on what caused it?

Below is the traceback for it:

com.glide.db.impex.json.JSONLoader: com.glide.db.impex.datasource.stream.StreamDataSourceException: No fields provided for mapping to headers: com.glide.db.impex.datasource.AbstractStreamLoader.getAttributes(AbstractStreamLoader.java:42)
com.glide.db.impex.AbstractLoader.createColumnAttributes(AbstractLoader.java:570)
com.glide.db.impex.AbstractLoader.createTableAndMap(AbstractLoader.java:324)
com.glide.db.impex.AbstractLoader.createTableForImport(AbstractLoader.java:296)
com.glide.db.impex.AbstractLoader.load(AbstractLoader.java:184)
com.glide.db.impex.AbstractLoader.startWork(AbstractLoader.java:166)
com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:131)
com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:26)
com.glide.worker.AbstractProgressWorker.start(AbstractProgressWorker.java:106)
com.glide.system_import_set.ImportSetLoader.startWorker(ImportSetLoader.java:141)
com.glide.system_import_set.ImportSetLoader.startLoader(ImportSetLoader.java:130)
com.glide.system_import_set.ImportSetLoader.loadImportSetTable(ImportSetLoader.java:76)
com.glide.system_import_set.ImportSetLoader.loadImportSetTable(ImportSetLoader.java:52)
com.snc.automation.ScheduledImportSetJob.doImport(ScheduledImportSetJob.java:188)
com.snc.automation.ScheduledImportSetJob.runImport(ScheduledImportSetJob.java:116)
com.snc.automation.ScheduledImportSetJob.runNextImport(ScheduledImportSetJob.java:86)
com.snc.automation.ScheduledImportSetJob.runImport(ScheduledImportSetJob.java:63)
com.snc.automation.ScheduledImportJob.execute(ScheduledImportJob.java:66)
com.glide.schedule.JobExecutor.lambda$executeJob$1(JobExecutor.java:194)
com.snc.db.data_replicate.replicator.DataReplicationAdvisors.runInOriginatorContext(DataReplicationAdvisors.java:73)
com.glide.schedule.JobExecutor.lambda$inDataReplicationContext$3(JobExecutor.java:224)
com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:197)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:177)
com.glide.schedule.JobExecutor.execute(JobExecutor.java:167)
com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:577)
com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$2(SchedulerWorkerThread.java:396)
com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35)
com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:396)
com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:172)

[Diogo Ramos]

Were you able to find on the logs when this happened? There were no extra logs ? Looking at that error I noted this description at the start of the log : 

No fields provided for mapping to headers

It could be related to bad content being received from your integration or a size too big to be handled or an issue on a field mapping or the path of your import for each row is not correct, hard to say without further info

I would try to first see if I find more logging information, then see what payload was sent for this call to validate the structure of the data. And then maybe look at the configuration of the import set / trying to replicate the call with postman and go from there. 

Good luck

[Hetang Modi]

No, these were the two logs present in the syslogs. As per my interpretation, I think the "Path for each row" doesn't match with content in the attachments of the data sources. However, some additional info somewhere would help much more find the actual cause.