github
/
apprise
mirror of https://github.com/caronc/apprise
1
0
Fork 0
Code Issues Releases Wiki Activity

Updated Troubleshooting (markdown)

master
Chris Caron 2020-01-20 08:09:15 -05:00
parent b106a297b8
commit 2ce07c18e9
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Troubleshooting.md

@ -36,9 +36,9 @@ python apprise --dry-run --tag=devops \
```
## Too Much Data and Overflow Directive
Out of the box, Apprise passes the full message (and title) you provide right along to the notification source(s). Some sources can handle a large surplus of data while others might not. All of the [supported notifications services](https://github.com/caronc/apprise/wiki#notification-services) Apprise supports have identify these limits on their respected wiki/help pages.
Out of the box, Apprise passes the full message (and title) you provide right along to the notification source(s). Some sources can handle a large surplus of data while others might not. These limitations are documented (*to the best of my knowledge*) on each of the [individual services corresponding wiki pages](https://github.com/caronc/apprise/wiki#notification-services).
However, if passing a large amount of data is still your goal: Apprise has a somewhat non-elegant way of handling this situation (it's better than nothing). You simply need to tack on the **overflow** parameter somewhere in your Apprise URL; for example:
However if you don't want to be bothered with upstream restrictions, Apprise has a somewhat _non-elegant_ way of handling these kinds of situations that you can leverage. You simply need to tack on the **overflow** parameter somewhere in your Apprise URL; for example:
* `schema://path/?overflow=split`
* `schema://path/?overflow=truncate`
* `schema://path/?overflow=upstream`