eMERGEncy

Ha! Get it? No actually this is just another pull request of standard urgency.
Oh yeah sorry. So the issue is that sometimes immediately after this step I update the status of the jobs in the local jobs database using [this command](https://github.com/NationalGenomicsInfrastructure/ngi_pipeline/blob/master/ngi_pipeline/utils/parsers.py#L50):

`"sacct -n -j {:d} -o STATE".format(slurm_job_id)`

So if there is no job with that job id, you get back just `""` (instead of `PENDING` or `RUNNING`), and I found that often during code execution it would get that unless I waited for a while and thus a run that I just launched would be marked as `FAILED`. This is a Bad Thing, so this is my workaround. I think it's just that the slurm database takes a little while to get things recorded properly. I don't know how else to approach it except for introducing a delay.