Thank you for the answer. I'm aware that I can download prepossessed gff files from ncbi (and it is the path I'm using for the bulk of the data).
The stated path is intended as complementary route for accessions which were not part of the initial data fetch (and are not present locally). The problem with some asn.1 files is that the sequence is not part of the asn.1 record, which causes asn2fasta to query it at some (I assume ncbi) server (otherwise the performance is OK).
I use efetch regularly I was not impressed with the asn2fasta performance, since the job it needs to do is basically efetch, as the accession number and other identifiers are present in the asn file.
It appears that I'll need to code some check if the sequence is part of the asn record and if not, just do plain efetch.
But thanks anyway
This really is a question for NCBI help desk. Be aware that it may take 2-3 business days to get an answer from them but be patient. Come back and post the official response here when you get one.