The fastest possible individual download is not always the best use of a shared connection. A long transfer can compete with calls, games, cloud sync and other downloads. Flux provides queue priorities, scheduling and shared or per-task limits so you can decide when tasks run and how much bandwidth they use.
Choose between starting and queueing
The approval window can add a task without immediately starting it. This lets you prepare names and destinations first, then run the queue at a more convenient time. Use task priorities for the file you need first instead of starting every available item at once.
Shared and per-task limits solve different problems
A per-task limit constrains one transfer. A shared budget keeps the group from consuming more than the intended total. Torrents can also use upload bandwidth, so consider both directions when the same connection serves other people. A limit is a budget, not a promise that the source will reach that speed.
Plan an unattended session carefully
- Confirm the output directory and available space.
- Set priorities and a suitable connection budget.
- Schedule the queue for the intended period.
- Review torrent sharing preferences.
- If enabling a completion action, check its countdown and cancellation controls.
Review what actually happened
Use the persistent history and task timestamps to see when a download was added, started and completed. An expired URL or unavailable peer can still prevent a scheduled task from finishing. Avoid treating a planned start time as a completion guarantee. The queue should make these conditions visible so you can act on individual tasks instead of losing track of an entire batch.
Sources and release context
This guide describes the Flux 2.6.6 documentation. Check the current release record for package conditions.
