No ".slc" file in the output of "run_12_merge_reference_secondary_slc" even though other files are exported

[Shima-shoki]

Hello, I've been working on InSAR analysis by using ISCE on Google Colab with GPU on recent days. I've managed to execute a list of processing chains produced by the stackSentinel.py from 6 Sentinel-1 SLC files. The problem is that there are {date}.slc.full, {date}.slc.full.aux.xml, {date}.slc.full.vrt, {date}.slc.full.xml, and {date}.slc.hdr, but no {date}.slc file in /merged/SLC/{date} folders after "run_12_merge_reference_secondary_slc".

The execution output at the "run_12_merge_referenec_secondary_slc" looks fine with the execution, and gdal.Translate also seems working (at least it doesn't show me an error).

Completed Parsing the Configuration file
Functions to be executed:
['Function-1']
Running: mergeBursts
['--stack', '/content/drive/MyDrive/SatelliteImageProcessings/InSAR_Python/ISCE2test-GPU/stack', '--inp_reference', '/content/drive/MyDrive/SatelliteImageProcessings/InSAR_Python/ISCE2test-GPU/reference', '--dirname', '/content/drive/MyDrive/SatelliteImageProcessings/InSAR_Python/ISCE2test-GPU/reference', '--name_pattern', 'burst*slc', '--outfile', '/content/drive/MyDrive/SatelliteImageProcessings/InSAR_Python/ISCE2test-GPU/merged/SLC/20230211/20230211.slc', '--method', 'top', '--valid_only', '--range_looks', '9', '--azimuth_looks', '3']
Updating the valid region of each burst to the common valid region of the stack
bursts:  1 2
Updating the valid region of each burst to the common valid region of the stack
bursts:  1 3
writing merged file to disk via gdal.Translate ...
0011....41....70....100 
Skipping multi-looking ....

Is this an expected phenomena, or am I doing something wrong...?
I'm pretty new to ISCE software, any kind help is very much appreciated!