Dynamic Start Behaviour

TORRENT-Watch-directories.md

@@ -7,8 +7,8 @@ Introduction
 To load torrent files dropped into special folders (by direct download, DropBox, ``scp``, ``sshfs``, and so on),
 you can extend your configuration with scheduled checks trying to load new files from these folders.
 
-Scheduled Task
---------------
+Watch Directory Schedules
+-------------------------
 
 These examples load items from different directories, in started state or idle.
 The 3rd example shows how to set a non-default download path, using a post-load command.
@@ -21,12 +21,24 @@ schedule2 = watch_directory_baz, 22, 10, "load.verbose=~/watch_baz/*.torrent,d.d
 
 The used *verbose* load commands log any problems to the console.
 Be aware though that half-written files can lead to spurious warnings,
-especially of your schedules have an interval like only 1 second.
+especially if your schedules have an interval like only 1 second.
 Use the ``load.start`` or ``load.normal`` commands instead 
 if you do *not* want any diagnostics.
 
 Also note that the start times are incremental, to spread the load caused by scanning the watch directories.
 
+Dynamic Start Behaviour
+-----------------------
+
+Sometimes you want to easily change whether an item loaded by a watch is started immediately or not. This is especially useful when combined with automatic downloaders like `FlexGet` or `autodl-irssi`.
+Usually, newly added items are started immediately – that is the whole point of automation.
+
+In some cases though, you might want to disable that and delay downloading until later.
+Testing configuration changes is a typical reason, because an innocent mistake could
+swamp you with lots of downloads. If they stay dormant at first, that is easily fixed.
+
+See [Watches With Dynamic Start Behaviour](https://pyrocore.readthedocs.io/en/latest/usage.html#watch-start) for how to set this up.
+
 
 Tied Files
 ----------