Troubleshooting batchloader

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ ls -alht | grep batchloader_elead -m 1
-rw-rw-r--  1 vitalsigns vitalsigns 5.1K Feb 24 19:52 batchloader_elead_20230224_195016842.log

Check if the last one has finished properly:

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ tail -f batchloader_elead_20230224_195016842.log
[...]
2023-02-24 19:57:45,257 [main] INFO  com.numinary.nxbatchloader.NxBatchLoader - End processing application SMRT CC Ops Elead, appId 15 
2023-02-24 19:57:45,257 [main] INFO  com.numinary.nxbatchloader.NxBatchLoader - Processing complete, exiting.

If it's been more than half an hour since the last log, stop the batchloader process manually.

vitalsigns@vitalsigns1:~$ ps aux | grep batchloader
vitalsi+  3505 71.4  0.6 14032548 447220 ?     Sl   13:01   0:10 java -Xmx11240M -jar nxbatchloader.jar appids=15 conffile=batchloader_elead.properties

Then kill the process with the pid (3505 in this example):

vitalsigns@vitalsigns1:~$ kill [pid]

If it hasn't finished check if it's still generating logs, in which case it's just a matter of time.
But if the process finishes and there's still missing data, check the webhooks.