Skip to content

fix(messaging): handle blocked accounts, contact scan limits and failed sends - #1718

Merged
viethung0o0 merged 6 commits into
mainfrom
feat/broadcast-stop-on-account-block
Nov 14, 2026
Merged

viethung0o0 merged 6 commits into
mainfrom
feat/broadcast-stop-on-account-block

Conversation

@viethung0o0

Copy link
Copy Markdown
Contributor

Summary

  • Broadcasts stop automatically when the channel account is blocked from sending; series are paused too, and Resume shows a warning with the reason.
  • Contact scan can be cancelled (UI and public API) and now waits according to the channel's API usage instead of sleeping in the worker.
  • Inbox: failed messages can be resent (UI and public API); a send error is shown only after retries are exhausted.
  • Messages typed quickly are sent one by one in order and held if one fails.

Test plan

  • Unit and database integration tests for broadcast stop, scan cancel and retry, resend and the send queue
  • Checked in the browser: stopped broadcast and Resume warning, scan cancel, resend of a failed message, sending from the inbox
  • pnpm lint, type checks for database, business, worker and builder
  • Check the Messenger 2022 error against real logs before merging

@github-actions github-actions Bot added the bug Something isn't working as expected label Nov 14, 2026
@viethung0o0
viethung0o0 marked this pull request as ready for review November 14, 2026 15:23
@viethung0o0
viethung0o0 merged commit 857aece into main Nov 14, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working as expected

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants