BUSCO 4.0.6 always (!) creates a download dir for each run. When multiple BUSCO analyses are run from the same root directory (e.g. busco_analyses/busco_proteins, busco_analyses/busco_transcripts, etc.) then checking if the download dir exists and creating it if not may collide across jobs, leading to a BUSCO run failure (this happens rarely, but it happens).
The issue was raised with the BUSCO developers (https://gitlab.com/ezlab/busco/-/issues/247), but this can also be circumvented by putting the configuration directories for the BUSCO runs into the individual run directories instead of into a common area.
BUSCO 4.0.6 always (!) creates a download dir for each run. When multiple BUSCO analyses are run from the same root directory (e.g. busco_analyses/busco_proteins, busco_analyses/busco_transcripts, etc.) then checking if the download dir exists and creating it if not may collide across jobs, leading to a BUSCO run failure (this happens rarely, but it happens).
The issue was raised with the BUSCO developers (https://gitlab.com/ezlab/busco/-/issues/247), but this can also be circumvented by putting the configuration directories for the BUSCO runs into the individual run directories instead of into a common area.