Telegram issue via netwatch after 7.12.1

RouterOS General
1

Hello

I have scripts that use another script with telegram function and working properly.
The Telegram function script inside has the command

/tool fetch url="https://api.telegram.org/MYBOT/sendMess ... &text=TEST"

All fine.

The same command I used to use the last years on Netwatch in UP or Down and it worked until update 7.13.
When I tried the same command from netwatch to terminal is working but not from netwatch.

Another interest thing with netwatch that into netwatch UP when I have this below is working the email sending but stack to “log info TEST Telegram netwatch”

:log error “TEST Email netwatch”
/tool e-mail send to=“MY EMAIL” subject=“MyDevice Up $[/system clock get time]”
:log info "TEST Telegram netwatch "
/tool fetch url=“https://api.telegram.org/MYBOT/sendMess … t=MyDevice Up”

If I reverse the script then it gets stuck in Telegram and doesn’t proceed to email either.
:log info "TEST Telegram netwatch "
/tool fetch url=“https://api.telegram.org/MYBOT/sendMess … t=MyDevice Up”
:log error “TEST Email netwatch”
/tool e-mail send to=“MY EMAIL” subject=“MyDevice Up $[/system clock get time]”


I don’t have any wrong error on log just stack to :log info “TEST Telegram netwatch”

What can I do for that? What you suggest?



The device is

routerboard: yes
board-name: cAP ac
model: RBcAPGi-5acD2nD
revision: r2
firmware-type: ipq4000L
factory-firmware: 6.44
current-firmware: 7.13.1
upgrade-firmware: 7.13.1

2

Here I have this same problem…
exactly the same, I don’t know what to do…
I updated all my production CCRs and didn’t want to downgrade

3

Same problem…
You solve it?

4

What I do, totally unrelated to netwatch, is that I let the scripts that generate the messages just push them to a queue, and I periodically schedule another script that reads the messages from the queue and sends them via Telegram; as there is a limit of number of Telegram messages per bot per unit of time, I aggregate the raw messages and send several of them as a single Telegram one. I also only remove the messages from the queue if the fetch succeeds, so if there is a temporary failure of Telegram communication or if I exceed the rate limit, no messages are lost.