Updated Troubleshooting (markdown)

Troubleshooting.md

@@ -12,6 +12,27 @@ If the output appears cryptic, or you feel that you've exhausted all avenues, Do
 
 Just be cautious as the debugging information can potentially expose personal information (such as your password and/or private access tokens) to the screen.  Please remember to erase this or swap it with some random characters before posting such a thing publicly.
 
+## Tag Matching Issues
+If you tagged your URLs, they're not going to be notified unless you explicitly reference them with **--tag=** (or **-g**).  You can always check to see what URLs have been loaded using the `all` tag directive paired with **--dry--run**:
+```bash
+# This simply lists all of the tags found in the apprise.txt file
+# You don't even need to specify the --config if you're reading files
+# from their default locations:
+python apprise --dry-run --tag=all \
+   --config=/my/path/to/my/config/apprise.txt
+
+# Without a --tag specified, you'll only match URLs that have
+# no tag associated with them:
+python apprise --dry-run \
+   --config=/my/path/to/my/config/apprise.txt
+
+# Otherwise, --dry-run can help you track what notifications are triggered
+# depending on what services you're targeting (without actually performing
+# any action):
+python apprise --dry-run --tag=devops \
+   --config=/my/path/to/my/config/apprise.txt
+```
+
 ## To Much Data and Overflow Directive
 Out of the box, Apprise passes _everything_ you give it right along to the notification source. Some sources can handle a large surplus of data; others might not deal with it as well and as a result, your notification doesn't seem to go through).