Bugs Fixed:

1) Preserving Opt-in Time During CSV Updates:

Earlier, when importing or moving contacts via CSV to update existing contacts, the optin_time was being updated by default. This was creating a confusion in the  user analytics. For example, a contact created and opted in during 2024 could appear as if they opted in at a later date.

This issue has been fixed: the optin_time will now remain unchanged unless explicitly updated, ensuring accurate tracking of user opt-ins.

2) Error sending message due to network issues or Gupshup outage:

Sometimes, messages were marked as `Error sending message due to network issues or Gupshup outage`. This happened when the client timed out while sending the message to Gupshup. Glific generates this error and attaches it to the message.

This bug has been addressed by implementing automatic retries for timeout errors, helping to improve message delivery success rates.

3) Inactive Flows Continuing Execution:

When a flow was marked as inactive, any users who were part of that flow should have their flow terminated immediately.
Previously, inactive flows continued to execute, causing unexpected behavior and incorrect messaging.This issue has been fixed: flows now terminate immediately when marked inactive, ensuring users only receive messages from active flows.

4) Simulator Assigned to Multiple Flows: 

Earlier, previewing a second flow while one was running in the simulator caused both flows to share the same simulator, leading to conflicts.

Now, each flow gets its own simulator per user.

5) Not able to close an open ticket:

We fixed the issue where open tickets couldn’t be closed (the interface got stuck at “Save button”). Now you can close tickets smoothly.

New Feature/Enhancements Done:

1) More Quick Reply Buttons in HSM Templates:

Previously, HSM templates on Glific allowed only up to 3 quick reply buttons. Now, you can create and apply templates with up to 10 buttons, sync them in Glific, and use them seamlessly within your flows.
This enhancement makes it easier to design more interactive and engaging conversations for your users.

2) Multi-User Flow Access in Read-Only Mode:

This was the most requested feature by NGOs, and here we have it!

The Flow Editor allowed only one user per flow. If a second user tried to open the same flow, they saw a pop-up with options to Go Back or Take Over, making it difficult for multiple team members to reference the same flow simultaneously.We have enhanced this now onwards second users can now view the flow in read-only mode.Editing is disabled for view-only users.A green colour banner in the top of the screen will indicate the view-only status.

3) Gupshup Credentials Form Becomes Read‑Only After Save:

In the Settings → Gupshup section, after saving Gupshup credentials like (App Name, App ID, API Key), the input fields used to remain editable.
This could cause confusion or accidental changes.

We have now fixed this so that once you save your Gupshup credentials, the fields automatically switch to read‑only mode.
This improves clarity and ensures your configuration status is properly locked in.

4) UI Improvement: Clearer header text in Staff Management:

We updated the column label from Assigned to → Collections assigned to make it easier to understand at a glance which staff member is assigned to which collection.

So that NGOs will find it more intuitive when managing staff roles and assigning collections, reducing potential misunderstanding.

In the Notification tab when you click on any particular error message action arrow, now it  opens in a new tab so you don’t lose your previous window. This improves navigation efficiency for NGOs, especially when reviewing multiple alerts or errors side‑by‑side.

Documentation Update:

Existing Documentation revamped:

We recently reviewed and revamped our documentation to make it more user-friendly.
The updated guides now include clear images, step-by-step instructions, and explanations of why each step is important. This makes it easier for NGOs to understand the purpose of each action and follow the process confidently. Please take a look at it here