Jobs pausing themselves

Yesterday (6/11, post-deploy) I started a job 1880. A few hours later, it appeared in the paused state, by itself (I didn't pause it).

I don't need that job to complete... instead I configured a new job (id 1889) and started that one late last night. But by this morning, it was 3% complete and in the paused state. I've resumed it, now, and will be watching it to make sure it continues running.

This is unexpected. I am not sure what could be causing that. Please keep me posted, by direct email if need be.

Aaron