Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Telegram - splitt messages
See original GitHub issue📣 Notification Service(s) Impacted Telegram
🐞 Describe the bug If too much log gets reported, it doesn’t work. So I won’t get any message. The message needs to get splitt into multiple messages if it hits the message limit of telegram.
At least I get the “too long” error on the next report run. But the previous message is lost until I manually check the systemd-journald.
💡 Screenshots and Logs
WARNING:apprise:Failed to send Telegram notification to {chat_id}: Bad Request: message is too long, error=400
💻 Your System Details:
- OS: Arch Linux
- Python Version: v3.10.8
🔮 Additional context Just too much message text for the telegram bot api.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Going to close this ticket off for now; the documentation needs to be updated; no question here.
The important part is hopefully you’re back in buisness
😄 Maybe a link to a general list above each table of the agent parameters