You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
modules.exceptions.FailedMessagesStatusUpdater: {'call': 'Thread-message-updater', 'message': 'Failed to update the message with the status of received messages ', 'users': [('123456789', '123456789')], 'user': ('123456789', '123456789'), 'exception': ApiTelegramException("A request to the Telegram API was unsuccessful. Error code: 400. Description: Bad Request: message can't be deleted for everyone")}
Additional context
Information about where the bug is happening:
The bot recreates the message every 24 hours, but for some reason it didn't work.
Possible correction
This problem shouldn't cause the thread to drop completely, if the message can't be deleted, you should just send a new one and replace it in the database.
The problem seems to be related to
## v2.1.6 - 2024-06-22
### What's Changed
**Full Changelog**: v2.1.5...v2.1.6 by @obervinov in #70
#### 💥 Breaking Changes
* remove unused database `environment` attribute permanent path in the Vault: `configurations/database`
* remove unused environment variable `PROJECT_ENVIRONMENT`
* the automatic queue verification mechanism has been removed. Instead of this method, added functionality to update the queue processing time via a message to the bot
* change the structure of the table `messages`: add a new column `state` and `updated_at`, rename column `timestamp` to `created_at`
#### 🐛 Bug Fixes
* #69
* #62
* #67
* #64
* #65
* Removed duplicates in rights checking
* Small refactoring code
#### 🚀 Features
* Bump dependency versions for modules and workflows
* Add button for rescheduling the queue
Describe the bug
Not working to renew
status_message
functionality in some situations.Log: https://obervinov312.grafana.net/goto/Mwwlj4yIR?orgId=1
Error message:
Additional context
Information about where the bug is happening:
Possible correction
This problem shouldn't cause the thread to drop completely, if the message can't be deleted, you should just send a new one and replace it in the database.
The problem seems to be related to
timestamp
is updated with each edit and the thread has no correct information about the post creation date.Screenshots
None
Check list after fixing the bug
created_at
database to record when the message was created and recreate it based on this attributeupdated_at
The text was updated successfully, but these errors were encountered: