Thank you for your explanations, it makes a lot more sense now. My guess is that your testing has been focused entirely on the "force quit" case This is exactly what we got wrong. We tested by force quitting the app w/o realizing that that's a different scenario from just going into the background. When we test by dragging up the app window and/or switching to a different app, it behaves as we expected and we do get reasonable background times as well. It would be great if the docs for this mentioned that it is not applicable for the "force quit" case to avoid confusion in the future. We'll do some more testing but for now we got the answers we needed, and we just have to accept that there's nothing we can do for force quitting and will have to have a robust recovery step on startup instead. Thanks again.