Does the Telegram option take into account API limits to prevent hitting 429 too many requests?

[rabid-dev]

I'm currently using apprise for some telegram notifications for my UPS Nut Server, so i can get alerts when ups enters battery/online mode. I also set them up when communications go bad or go ok.

For some reason specific to my setup, sometimes a UPS commbad event arrives and very shortly after (probably less than a second after) another UPS commok event arrives, making it so 2 Telegram notifications are sent very quickly, however i've noticed that i only receive one on my Telegram chat, whereas on the syslogs of my machine the 2 events appear, so i was wondering if one of them may be getting error 429 too many requests as i know that Telegram limits messages to 1 per second.

So does Apprise take Telegram bot limits into account and apply some sort of batching? Or shoudl I implement my own solution in front of it so i dont miss a message?

[caronc]

It looks like the (Apprise) Telegram plugin doesn't support the 429 response (a lot of Apprise plugins do), where the payload of this message also includes the time it's 'safe' to post again (to which Apprise retries automatically for you).

Wouldn't involve tooooo much effort since there are lots of plugins to base this off of. You wouldn't happen to have a sample of the payload response Telegram sends would you (when you get a 429?). If you're using the Apprise CLI, you can just stick in extra -vvvv switches on your call to increase the verbosity.

[rabid-dev]

Thanks for the answer! I'm currently out of town, so I'll try to have an example of the payload response when i come back. However, these days I've been testing and I've gotten mixed signals because I remember having issues when i posted the question, but now i even tried sending 10 messages in rapid fire and no one got 429 too many requests message... so I don't know, maybe it's inconsistent

As soon as i get the example payload i'll make sure to post it here