Our issue was caused by a variable with a user prompt input that wasn't being populated when we scheduled the report. When we removed the variable the report started scheduling just fine.
This was not an issue before we upgraded to 4.1 from 4.0.
I hope this helps someone!