how to re-run workflows when some samples fail?

I have a fairly simple workflow with 2 tasks. The second task depends on the output produced by the first. If I look at the output tab on the workspace workflow tab I see the output is configured correctly

As a test, I ran it on 10 samples, 2 failed on the first task because there was not enough memory. I selected the original data set, set the runtime to use more memory and re-ran everything

"use call caching" was on for all submissions

Using the job manager this is what I see for one of the samples that completed successfully durring the first submission

Notice the duration of the second task is zero. This is what I expected. the result was calculated correctly in the first submission.

Notice that first task has a duration of 30 min. This was unexpected. The result of this task was populated to the sample table and completed successfully during the first submission

workflow quantify {
    String sampleId
    File inputBam
    File refIndexTarGz
    
    call bamToFastq.bamToFastq {
        input:
        inputBam=inputBam,
        sampleName=sampleId
    }

    call salmonPairedReadQuantTask.salmon_paired_reads {
        input:
        sampleId=sampleId,
        refIndexTarGz=refIndexTarGz,
        leftReads=bamToFastq.firstEndFastq,
        rightReads=bamToFastq.secondEndFastq,

        # see salmonPairedReadQuantTask.wd for more information aobut
        # choosing parameter values
        outDir="salmon.out",
        dockerImg='quay.io/biocontainers/salmon:1.4.0--hf69c8f4_0',
        memoryGb=64,
        diskSpaceGb=80,
        runTimeCpu=8,        
        runTimePreemptible=3
    }
}

Is this a bug or expected behavior?

Kind regards

Andy

p.s. When I ran the workflow for the first time, I aborted it after about 30 mins. I realized one of the inputs needed by the second task was configured to use a google bucket it probably did not have access to. It took a surprising amount of time for it to complete the abort request. I wonder if this had something to do with the unexpected behavior?