A delivery the channel rejects for good is retried forever, and a long notice never reaches Telegram #2016
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#2016
Reference in new issue
Block a user
A notice longer than Telegram allows (about 5000 characters against its 4096 limit) fails with "message is too long" on every attempt. Deliveries treat that as transient and retry it indefinitely (attempt 41 seen on staging), so the notice is never seen and the retry loop never ends.
Two parts: the telegram connector splits or trims a message to the channel limit, and the connector contract lets a connector report a permanent failure so deliveries stop retrying and record it as failed where the trail shows it.
Done when: a long investigation notice arrives on Telegram, and a delivery rejected permanently stops after one attempt with its reason visible.
Fixed in archie-core
b48616798andf47e60db0(migration 00043), and archipelago a69f713 and 6d2363c.InvalidArgument,FailedPrecondition,PermissionDeniedorNotFoundwhen the service rejects a delivery permanently. Any other status is retried. Status codes needed no new field inDeliverResponse.failed_at) after that attempt, with its reason in the attempts list, so the dashboard trail shows it. Other failures keep the backoff but stop after 150 attempts, about a day with the 10-minute cap, and the reason is prefixed "gave up after N attempts".Verified: the changed packages pass vet, tests and lint in both repos, and
task checkpassed on the merged archie-core tree. The retry loop has no test, because it needs the database. Not verified on staging: a long investigation notice arriving on Telegram, and a permanently rejected delivery stopping after one attempt.