These are chat archives for nextflow-io/nextflow
@pditommaso So I think I know where the bottleneck is: I did not have any AWS batch job for the tasks I submitted - and when I launched all 50 samples the engine somehow got hung up - because no jobs where submitted and also no job description was created. then I repeated the process only on one sample which then actually got submitted and a job description created. with the job description being available, when I later tried all 50 samples it worked without problem. Could this be the reason?
@t-neumann I can verify exactly the same behaviour. submit 300 jobs - it hangs. Later I submitted 2 test jobs and it's OK. Then go back and submit the 300 and they submit, whereas previously it hung.