JDBC Data Source error associated with flow action - javax.json.JsonException: Cannot auto-detect encoding, not enough chars - Support and Troubleshooting

JDBC Data Source error associated with flow action - javax.json.JsonException: Cannot auto-detect encoding, not enough chars Issue If you try to manually load the data using the "Load All Records" or "Test Load 20 Records" records from a JDBC data source associated with a flow action, you will receive the below error. However, executing the flow action directly will not return any error and the data will be retrieved as expected.

If you trace the transaction log you can see the below errors however associating the data source with the flow action works fine when tested via the flow designer directly and it returns data in an object.

2024-02-28 15:54:51 (053) worker.0 worker.0 txid=d431178736b9 Completed: ImportProcessor in 0:00:01.188, next occurrence is null, id=dc31578787e84a50cc6b1fc83cbb3534 tr=0 pr=25 re=0 po=1709164489 la=0.855 2024-02-28 15:54:51 (029) worker.0 worker.0 txid=d431178736b9 SEVERE *** ERROR *** load failed! See import log for error messages 2024-02-28 15:54:51 (006) worker.0 worker.0 txid=d431178736b9 WARNING *** WARNING *** Error during data load, skipping application module creation 2024-02-28 15:54:50 (993) worker.0 worker.0 txid=d431178736b9 WARNING *** WARNING *** javax.json.JsonException: Cannot auto-detect encoding, not enough chars 2024-02-28 15:54:50 (979) worker.0 worker.0 txid=d431178736b9 SEVERE *** ERROR *** com.glide.db.impex.json.JSONStreamLoader com.glide.db.impex.datasource.DataSourceException: javax.json.JsonException: Cannot auto-detect encoding, not enough chars at com.glide.db.impex.json.JSONLoader.initParser(JSONLoader.java:109) at com.glide.db.impex.json.JSONStreamLoader.preLoad(JSONStreamLoader.java:18) at com.glide.db.impex.AbstractLoader.createColumnAttributes(AbstractLoader.java:570) at com.glide.db.impex.AbstractLoader.createTableAndMap(AbstractLoader.java:325) at com.glide.db.impex.AbstractLoader.createTableForImport(AbstractLoader.java:297) at com.glide.db.impex.AbstractLoader.load(AbstractLoader.java:185) at com.glide.db.impex.AbstractLoader.startWork(AbstractLoader.java:167) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:131) at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:26) at com.glide.worker.AbstractProgressWorker.start(AbstractProgressWorker.java:106) at com.glide.processors.ImportProcessorWorker.startWorker(ImportProcessorWorker.java:331) at com.glide.processors.ImportProcessorWorker.loadDataSource(ImportProcessorWorker.java:172) at com.glide.processors.ImportProcessorWorker.startWork(ImportProcessorWorker.java:110) at com.glide.worker.AbstractProgressWorker.startAndWait(AbstractProgressWorker.java:131) at com.glide.worker.HierarchicalProgressWorker.startAndWait(HierarchicalProgressWorker.java:26) at com.glide.worker.BackgroundProgressJob.execute(BackgroundProgressJob.java:59) at com.glide.schedule.JobExecutor.lambda$executeJob$0(JobExecutor.java:169) at com.glide.schedule.JobExecutor.executeJob(JobExecutor.java:172) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:155) at com.glide.schedule.JobExecutor.execute(JobExecutor.java:149) at com.glide.schedule_v2.SchedulerWorkerThread.executeJob(SchedulerWorkerThread.java:449) at com.glide.schedule_v2.SchedulerWorkerThread.lambda$process$1(SchedulerWorkerThread.java:318) at com.glide.worker.TransactionalWorkerThread.executeInTransaction(TransactionalWorkerThread.java:35) at com.glide.schedule_v2.SchedulerWorkerThread.process(SchedulerWorkerThread.java:318) at com.glide.schedule_v2.SchedulerWorkerThread.run(SchedulerWorkerThread.java:118) Caused by: javax.json.JsonException: Cannot auto-detect encoding, not enough chars at org.glassfish.json.UnicodeDetectingInputStream.detectEncoding(UnicodeDetectingInputStream.java:131) at org.glassfish.json.UnicodeDetectingInputStream.(UnicodeDetectingInputStream.java:76) at org.glassfish.json.JsonParserImpl.(JsonParserImpl.java:76) at org.glassfish.json.JsonProviderImpl.createParser(JsonProviderImpl.java:83) at javax.json.Json.createParser(Json.java:104) at com.snc.json.xpath.SNXPathNavigatorJSON.getDocument(SNXPathNavigatorJSON.java:59) at com.glide.communications.json.JSONStreamParser.(JSONStreamParser.java:56) at com.glide.db.impex.json.JSONLoader.initParser(JSONLoader.java:106) ... 24 more Cause The reported error can occur if the 'Save as Attachment' is not being set to 'TRUE' automatically by default in the "sys_hub_step_instance" table for the action that is associated with the data source i.e. against the Request Action field.

Resolution After publishing the flow that has the REST data source associated, navigate to the 'sys_hub_step_instance' table and validate if the 'Save as Attachment' field is enabled or not.

Use the below URL, replace the sys_id with the actual sys_id of the Request Action as used in the data source

https://instancename.service-now.com/sys_hub_step_instance_list.do?sysparm_query=label%3DData%20Source%20Request%5Eaction%3Dsys_id