Release notes
Kalahamoon 2.30.3
Reliable messaging replies, focused Bale connection settings, mobile search keyboard handling, and faster deployments.
Kalahamoon team
Kalahamoon 2.30.3
Move Bale messages to Conversations while preserving connection management and recipient permissions. Keep mobile search within the visible screen when the keyboard opens or pans. Includes the pending WhatsApp and Telegram connection repairs, userbot replies without a Telegram bot, page performance improvements, self-hosted CAPTCHA, and a smaller shared migration runtime.
Focused Bale connection settings
Manage connection and recipient permissions in settings; read and reply to messages in Conversations.
Mobile search stays visible above the keyboard
Track the visible viewport when the mobile keyboard opens, resizes, or pans; keep the search input fixed within the dialog. Remove the duplicate search entry from the mobile navigation drawer.
Stable page hydration and administrator analytics exclusion
Keep session and theme providers mounted consistently, use responsive shell spacing, and stop Clarity for excluded administrators and routes.
Tenant context and queue health
Preserve request context when database connections are assigned to waiting requests. Report excessive product matching backlogs and avoid recovery jobs for work already queued.
WhatsApp and Telegram connection recovery
Recover retired Chromium locks, deliver WhatsApp QR codes through status polling, restore Telegram userbot sessions, confirm real disconnects, and recognize userbot connections in the inbox.
Self-hosted store CAPTCHA
Protect public store lead forms with bounded challenges, rate limits, and replay protection using self-hosted ALTCHA.
Faster deployment and leaner release retention
Package only migration runtime dependencies and share one image between migration and release import. Retain one validated rollback release by default.
Bale account replies and outgoing message synchronization
Recognize connected Bale user accounts without requiring a bot. Synchronize messages sent from the Bale account as outgoing messages and deduplicate CRM reply echoes. Invalid webhook events are preserved separately so they cannot block later valid messages.