NewMessage event not working for majority of channels all of a sudden

[himanshuj89]

Hi,

I am subscribed to 20+ Telegram channels and I was receiving all new messages until 2 days back without any issues.

Since Yesterday, I am not receiving message for NewMessage event for most of the channels. I didn't make any changes in the code.

I am only receiving this for 1-2 channels and not others. On Telegram app, I can see messages on almost all channels.

I am using below line of code for subscribing to all new messages -

client.addEventHandler(eventFunction, new NewMessage({}));

Any idea if Telegram updated something at their end?

thanks.

[boltpl81]

I thought that I messed something in the code, but it looks like it's genereral problem.
btw. it looks like a problem with channels with huge number of subscribers. Small channels are being triggered like before

[himanshuj89]

Yes, correct. In my case, I am getting messages through event for channels with subscriber count around 1000 but not for channels with subscriber count more than 30000.

[boltpl81]

Couple of minutes ago I've received event from huge channel. Maybe some hickup on telegram end? I'm going to monitor the behavior.

[GuilhermeGabriel]

The same here

[justalike]

can confirm, this happened to me as well.

So I've noticed that connection was established using Layer 159 which is kinda outdated?

So what I've done:
Tried to do hard reinstall of the library by

• removing it with npm remove telegram and
• reinstalling back with npm install telegram

Now logs say Layer 179 is used for connecting.
All of a sudden got a message from the channel with 25k+ subscribers.

Tested out (not too extensively though)

So update your lib to "telegram": "^2.21.2" to test it out.

Fixed the issue for me with no code changes.

[SwatX18]

can confirm, this happened to me as well.

So I've noticed that connection was established using Layer 159 which is kinda outdated?

So what I've done: Tried to do hard reinstall of the library by

• removing it with npm remove telegram and
• reinstalling back with npm install telegram

Now logs say Layer 179 is used for connecting. All of a sudden got a message from the channel with 25k+ subscribers.

Tested out (not too extensively though)

So update your lib to "telegram": "^2.21.2" to test it out.

Fixed the issue for me with no code changes.

Still not working for me...

[nickuya]

I was running into the same issue. When I started up my program, I would receive new messages for my large channels but after about 2 minutes it would stop.

One day I left the program running anyways, and then after about 10-20 minutes I noticed a timeout error in my logs and started receiving new messages again. I tracked down the timeout to here

gramjs/gramjs/client/updates.ts

Lines 245 to 260 in 5a0f45b

	} catch (err) {
	// eslint-disable-next-line no-console
	if (client._errorHandler) {
	await client._errorHandler(err as Error);
	}
	if (client._log.canSend(LogLevel.ERROR)) {
	console.error(err);
	}
	lastPongAt = undefined;
	if (client._sender!.isReconnecting || client._isSwitchingDc) {
	continue;
	}
	client._sender!.reconnect();
	}

so something in there seemed to kickstart the ability to receive messages again.

using that, I implemented an interval to just call the same reconnect method as at the bottom of that error handler.

setInterval(async () => {
  client._sender?.reconnect();
}, 1000 * 60);

bit of a hack. seems like it's possible to end up missing messages, but for my purposes seems to work so far.

Hope it works for others.

[sbeben]

same here
also, the workaround proposed by @nickuya does not work as reconnects are never successful for some reason
version 2.26.7
layer 193

[MishaMgla]

Experiencing same issue. With some messages it works flawlessly, with some NewMessage event is never triggered.