I used not being able to contact the remote site as an example -- it's not the only thing that can block an import! A technical issue is entirely possible, but since other imports are completing successfully, it's not a guarantee and if an issue does exist, it's only an issue with importing from your LJ account. (Most commonly, because something about the data in your LJ account is irregular, malformed, or otherwise unexpected -- after ten years, the importer is pretty hardened against "stuff it didn't expect to find", but LJ's been accepting data for so long and has gone through so many changes in terms of what's accepted, what's cleaned, and what's rejected that even after a decade we're still being presented with edge-case data.) In cases like that, the problem will need one-on-one troubleshooting and debugging that can take hours and needs to be done by one of two people, both of whom are very busy, and it can take a long time for one of them to have the time to troubleshoot an i
ndividual import problem. Please wait out the 7 day cycle, check your on-site inbox (https://www.dreamwidth.org/inbox) for any error messages -- they won't necessarily be sent to your email -- and then open a support request, including the text of any inbox messages you've gotten.
The "your previous import job will be aborted" applies only if the past job has been scheduled but not started. If some, but not all, of your comments have been imported, scheduling a new import doesn't abort the old one, because otherwise someone will lose their place in the import queue. I took a look, and the comments task for the first import you scheduled a few days ago did fail and is waiting out the delay for the next retry. There should be a message in your inbox to give you more information.
no subject
I used not being able to contact the remote site as an example -- it's not the only thing that can block an import! A technical issue is entirely possible, but since other imports are completing successfully, it's not a guarantee and if an issue does exist, it's only an issue with importing from your LJ account. (Most commonly, because something about the data in your LJ account is irregular, malformed, or otherwise unexpected -- after ten years, the importer is pretty hardened against "stuff it didn't expect to find", but LJ's been accepting data for so long and has gone through so many changes in terms of what's accepted, what's cleaned, and what's rejected that even after a decade we're still being presented with edge-case data.) In cases like that, the problem will need one-on-one troubleshooting and debugging that can take hours and needs to be done by one of two people, both of whom are very busy, and it can take a long time for one of them to have the time to troubleshoot an i ndividual import problem. Please wait out the 7 day cycle, check your on-site inbox (https://www.dreamwidth.org/inbox) for any error messages -- they won't necessarily be sent to your email -- and then open a support request, including the text of any inbox messages you've gotten.
The "your previous import job will be aborted" applies only if the past job has been scheduled but not started. If some, but not all, of your comments have been imported, scheduling a new import doesn't abort the old one, because otherwise someone will lose their place in the import queue. I took a look, and the comments task for the first import you scheduled a few days ago did fail and is waiting out the delay for the next retry. There should be a message in your inbox to give you more information.