An option to wait for WiFi would fit this use case too. Your prepaid data example shows why a transfer that resumes correctly can still need a clear choice before it uses mobile data again
That’s a good point. SEYFR should not finish someone’s data bundle just because it can resume. In this test I turned mobile data back on myself, but an option to "wait for Wi-Fi " makes sense. It would give people more control over when the transfer resumes. Thank you for pointing that out Crownforge .