Read the actual prompt and destination
Roku’s Bandwidth Saver documentation describes a confirmation after four hours without commands from the Roku remote or mobile app. If unanswered, the device can leave the streaming app, return to Home and stop downloading the stream.
An application can separately ask for viewing confirmation or stop its own autoplay. Record the message wording, whether it names a service, how long the session ran and whether the device returned to Home. Those observations help distinguish a Roku-level prompt from a control implemented inside the programme application.
Inspect the platform preference once
Roku documents Bandwidth Saver under Home, Settings, Network, Bandwidth Saver. Check its actual state on the supported device. Its source also explicitly says that turning this feature off does not affect independent inactivity mechanisms used by some streaming apps.
Do not treat that control as a universal command to make every service play indefinitely. If the platform preference is already off and the application still presents a confirmation, use the service’s own help for that exact message. Keep the two settings and their different owners clear in your support notes.
Choose a useful session plan
If you are actively watching, answer the visible confirmation using the appropriate device or app controls. If the screen has been left unattended, a stopped stream may already match the intended data-saving behaviour. Decide which result you actually want before changing a preference.
For help, provide the Roku model, Bandwidth Saver state, app, prompt wording and the result of confirming it. Avoid claiming a network fault simply because an unattended session stops after a long interval. The layer-specific evidence is more useful than repeatedly reinstalling an app or assuming one device setting overrides its provider’s own viewing controls.