Open vadimkerr opened 1 year ago
This issue will already make this problem googlable :)
I got this problem. After the failed deployment, telegram was sending once per minute POST messages. I cleaned everything in oncall and made a new deployment, but telegram continued to send POST requests and this caused my oncall to work incorrectly: I could not bind a telegram channel to oncall, alerts did not have "Acknowledgement", "Resolve" buttons ... I had to change the external port to another one so that old POST messages do not arrive on the port that the oncall engine is listening on. After that I was able to run oncall without errors
I got this problem. After the failed deployment, telegram was sending once per minute POST messages. I cleaned everything in oncall and made a new deployment, but telegram continued to send POST requests and this caused my oncall to work incorrectly: I could not bind a telegram channel to oncall, alerts did not have "Acknowledgement", "Resolve" buttons ... I had to change the external port to another one so that old POST messages do not arrive on the port that the oncall engine is listening on. After that I was able to run oncall without errors
I have the same problem. Alerts are sent to the channel, but there are no messages/buttons in the discussion
Currently the Telegram webook endpoint returns 500 and
TypeError: 'NoneType' object is not iterable
error in logs whenTELEGRAM_TOKEN
is unset. The error should be human-readable and suggest to set theTELEGRAM_TOKEN
env variable.Example: