-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request invoked too often #3
Comments
Maybe you just tried many consecutive times? Or trying have multiple telebagger instances working at same time? |
Hmm yeah could be multiple instances. Is there a way to run multiple
instances without being invoked?
…On Wed, 13 Jun. 2018, 8:08 am tomillo, ***@***.***> wrote:
Maybe you just tried many consecutive times? Or trying have multiple
telebagger instances working at same time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AOjtC3vBUHdAvtLwZ9lvyxm6_2ZWDzP2ks5t8FgWgaJpZM4UlU29>
.
|
I just tried one every 10 minutes |
Would there be a way to have multiple channelids and webhooks in the one bot? Something like that? |
I would also like that function to be developed by @davidmckenzie 🤓 |
Just tried the updated version and I'm getting.
06-13 01:52 telethon.telegram_bare_client INFO Invoking ['GetHistoryRequest(peer=InputPeerChannel(channel_id=1111111, access_hash=-11111111), offset_id=0, offset_date=None, add_offset=0, limit=50, max_id=0, min_id=31, hash=0)'] failed 1 times, connecting again and retrying 06-13 01:52 telethon.telegram_bare_client INFO Reconnection aborted: already connected 06-13 01:52 telethon.telegram_bare_client WARNING Request invoked too often, wait 23s
Have changed, channel_id and Access_hash.
Seems to only do it on this updated one.
The text was updated successfully, but these errors were encountered: