Bugs Fixed:

1. HSM Template Sync Timeout: Raised By1 NGO Udhyam:

Syncing HSM templates was failing for organisations with large volumes of template messages (e.g., with 1000+ templates), due to API timeouts.

To fix this we made the template syncing a background process.

2. Bulk HSM Template Apply was failing with buttons:

 While applying HSM templates in bulk failed when templates included buttons (has_buttons: true).

The extraction and processing of button fields have been improved, and this issue is now resolved.

3. Table Sync Failure to BigQuery (BQ):

Some organizations’ tables were not syncing because their last_communication_at timestamp was older than 12 hours—common in WA group-only orgs.

We updated a logic to better track organization activity by automatically updating timestamps when new messages are added.

4. Null Message Sent When Responding with Emoji:

Previously Bot responded with a null message when replying using emojis.

We have standardised the API to return an empty string (“”) instead of null if a message is replied by an emoji.

5. Big Query (BQ) Sync Stuck on Simulator Contact Rows:

The sync stalled when only simulator contact rows were fetched repeatedly.

To fix this we skipped simulator rows efficiently and improved handling of empty data chunks.

6. Unable to switch between collections:

On the Collections page, users could not switch to a selected collection—only the default collection was visible.

The following actions were taken to resolve this issue.

• Improved selection logic to retain the chosen collection in collection mode.
  
• Enhanced conversation fetching to ensure group conversations load correctly.
  
• Updated cache logic to match based on entity or collection ID where applicable.

 New Feature/Enhancements Done:

1. Logging Language Changes During Contact Import:

While performing bulk import or moving contacts, earlier we didn’t log language changes—unlike other contact fields such as name. Logging language changes would help in tracking and auditing updates more effectively.

Hence to fix this we added logging for language changes to improve tracking.

2. Prevent Duplicate Buttons in Interactive Templates:

Interactive message templates allowed buttons with identical content, which could lead to UI confusion and unexpected behavior.

The following actions were taken to resolve this issue.

• Added validation to ensure all button labels are unique within a quick reply template.
  
• Introduced clear error messages when duplicate labels are detected, promoting better UX and template consistency.
  
  
  

3. Tag Persistence on Flow and Template Creation:

When a new interactive message or HSM template flow was created and saved, users were redirected back to the list page—but the previously selected tags were cleared. Additionally, tags for HSM templates were not functioning as expected.

Fixes Implemented:
Now, when navigating to the creation page from a list with selected tags, those tags will be auto-populated on the creation page.After saving the new template/flow and returning to the list page, the previously selected tags will remain intact.Tag selection and usage for HSM templates now work as intended.

Important Platform Updates:

1. Deprecated Meta Checkbox from Template UI:

The `Allow Meta to re-categorise template` checkbox was still shown on the
Create New Template page, though it’s no longer supported by Meta.

Removed this obsolete option from the HSM/ Template section

2. Expired Option Removed from “Enter a Flow” Node:

The `expired`condition was previously unsupported in the Enter a Flow node but was
still present.
Hence removed the unsupported “expired” option to align with actual functionality.

Documentation Update:

1. How to setup HSM delivery dashboard:

We had received several queries from NGOs about how to identify the number of contacts who did not receive the business-initiated message due to Meta’s frequency capping on Marketing HSMs.

To help you understand this better, we have added detailed information in the documentation here.