The default resource timeout is 7 days, and I generally recommend that you leave that as it is unless you have a specific reason to change it.
The background error we see is 1001 (request timeout). I know you had recommended setting the timeout to 1 day.
There’s two possibilities here:
I’m thinking that A doesn’t apply because you doing a download (a GET). Is that still the case? If you start doing non-retrying things (like a PUT or a POST), you have to worry about the request timeout.
With regards B, the way you’ve described things it sounds like the task failed before the resource timeout hit. That is, you have a sequence like:
Sometime during the day, you started a task with a resource timeout of 1 day.
You came in the next morning to find the request has failed.
That’d be weird, because the one day resource timeout should only affect you when you get to the time of day for step 1.
Regardless, the first step in my investigation would be to use a packet trace to see what’s happening on the ‘wire’. For example, I’ve seen situations where a retryable request would never complete because:
It was not resumable.
The throughput was so slow that iOS kept deferring the task.
Each time it was deferred, it had to start from the beginning because it couldn’t resume where it left off.
Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware
let myEmail = "eskimo" + "1" + "@apple.com"