when organism name changes we need to migrate such that the jobs dont fail. could we do that? or at least give them the option to rerun like we do with steps? something better than what we do now..
New multiblast will return a different error when the organism name changes. Specifically it will return a 410 Gone error because the backing blast file is "gone" as far as mblast can tell
when organism name changes we need to migrate such that the jobs dont fail. could we do that? or at least give them the option to rerun like we do with steps? something better than what we do now..