It will continue to retry, it just won't retry the failed message (the integration doesn't disable itself; just marks that an error occurred. That error will clear on the next success).
can't parse entities: Can't find end of the entity is a telegram error indicating an issue with formatting/characters in the message.
Retrying to clear transient errors is reasonable, though; I'll add that.
It will continue to retry, it just won't retry the failed message (the integration doesn't disable itself; just marks that an error occurred. That error will clear on the next success).
`can't parse entities: Can't find end of the entity` is a telegram error indicating an issue with formatting/characters in the message.
Retrying to clear transient errors is reasonable, though; I'll add that.
<!-- github-comment-id:4339242445 -->
Keeping this open for feedback, but the issue you're having won't resolve until the message string is patched up 🙂
Keeping this open for feedback, but the issue you're having won't resolve until the message string is patched up 🙂
<!-- github-comment-id:4339473125 -->
i'm not sure what's wrong with my message string :)
it's working most of the time and fails only in some strange rare cases. i have feelings it's somehow related to unicode chars in username. i will monitor this more
i'm not sure what's wrong with my message string :)
it's working most of the time and fails only in some strange rare cases. i have feelings it's somehow related to unicode chars in username. i will monitor this more
<!-- github-comment-id:4343210655 -->
i'm using markdown mode. but {sender_name} is not escaping anything within it.
so when username is, for example, John_Snow, markdown brokens
not sure who to blame, probably mr. Durov, will try to migrate to html messages instead of markdown
okay, i finally figured out my problem:
i'm using markdown mode. but {sender_name} is not escaping anything within it.
so when username is, for example, John_Snow, markdown brokens
not sure who to blame, probably mr. Durov, will try to migrate to html messages instead of markdown
<!-- github-comment-id:4343899316 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
this way on error integration silently disables itself and not enables it after
It will continue to retry, it just won't retry the failed message (the integration doesn't disable itself; just marks that an error occurred. That error will clear on the next success).
can't parse entities: Can't find end of the entityis a telegram error indicating an issue with formatting/characters in the message.Retrying to clear transient errors is reasonable, though; I'll add that.
Keeping this open for feedback, but the issue you're having won't resolve until the message string is patched up 🙂
i'm not sure what's wrong with my message string :)
it's working most of the time and fails only in some strange rare cases. i have feelings it's somehow related to unicode chars in username. i will monitor this more
okay, i finally figured out my problem:
i'm using markdown mode. but {sender_name} is not escaping anything within it.
so when username is, for example, John_Snow, markdown brokens
not sure who to blame, probably mr. Durov, will try to migrate to html messages instead of markdown
Ahhh interesting. Maybe I can make an option for escaping markdown syntax
Added a friendlier option for ya 🙂