find_homolog_genes.py errors without explanation

[anoronh4]

Hello! i am finding that fusioncatcher consistently exits out without explanation. The end of my log looks like this:

////////////////////////////////////////////////////////////////////////////////
  Running: step = 214   Time: 11:02   Date: 2025-10-12 (elapsed time: 0d:5h:17m)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
==> Current working directory: '/localscratch/nxf.WCe5IoYNyY'
find_homolog_genes.py \
--input /localscratch/nxf.WCe5IoYNyY/reads_filtered_all-possible-mappings-transcriptome_multiple_sorted.map \
--reads 1 \
--input_exons /localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/exons.txt \
--filter /localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/custom_genes_mark.txt \
--processes 12 \
--output /localscratch/nxf.WCe5IoYNyY/list_candidates_ambiguous_homologous_genes_2.txt
--------------------------------------------------------------------------------
+-->EXECUTING...


ERROR: Workflow execution failed at step 214 while executing:
----------------
   find_homolog_genes.py \
   --input /localscratch/nxf.WCe5IoYNyY/reads_filtered_all-possible-mappings-transcriptome_multiple_sorted.map \
   --reads 1 \
   --input_exons /localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/exons.txt \
   --filter /localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/custom_genes_mark.txt \
   --processes 12 \
   --output /localscratch/nxf.WCe5IoYNyY/list_candidates_ambiguous_homologous_genes_2.txt
----------------
  * Size '/localscratch/nxf.WCe5IoYNyY/reads_filtered_all-possible-mappings-transcriptome_multiple_sorted.map' = 5350335336 bytes
  * Size '/localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/exons.txt' = 172554518 bytes
  * Size '/localscratch/nxf.WCe5IoYNyY/fusioncatcher_human_v102/custom_genes_mark.txt' = 6 bytes
  * Size '/localscratch/nxf.WCe5IoYNyY/list_candidates_ambiguous_homologous_genes_2.txt' = 0 bytes


Executing second time the same step/command in order to capture error messages (i.e. STDERR)...

-------------------------------------------


WARNING: First execution ended with error but second execution did not! Therefore cannot capture the STDERR!
################################################################################
################################################################################
TOTAL RUNNING TIME: 0 day(s), 6 hour(s), 32 minute(s), and 28 second(s) 
################################################################################
################################################################################

The pipeline has been attempted twice and both times the first attempt will error and the second attempt to capture the error does not. Not sure how to debug this? the error code at workflow exit is 1. I suspect that this is a memory issue, just wondering if there's a way to get the exit code to be more informative?