Bugs Fixed:

1) Bhashini API – Issue with Voice Notes Longer than 30 Seconds

The Bhashini API was unable to process voice notes longer than 30 seconds, either returning a 500 error or only partially processing the voice note.

To address this issue, we consulted with the Bhashini team. They suggested enabling Voice Activity Detection (VAD) by adding “preProcessors”: [“vad”].
This VAD function allows audio files longer than 30 seconds to be processed by identifying voice activity, ensuring that only relevant audio is processed.
This reduces load and enhances the ASR system’s efficiency.

2)  Template flows are showing up in active flows:

As you may know, we introduced template flows (pre-designed flows) to make it easier for you to view and customize them to suit your needs.
Template flows were appearing in both the sections – active and template flow, though ideally, it should only appear in one of these sections. As template flows were showing as active, there was risk that it might be mistakenly deleted or cause confusion.
Additionally, template flows are intended to remain unchanged to preserve their purpose.

Moreover, the filters weren’t functioning correctly. The search function produced different results when using uppercase letters compared to lowercase letters.

We resolved this issue by maintaining a clear separation between active and template flows. The filters in the flows API have also been fixed, allowing for easier flow name searches.

3) Triggers were not working due to large collection size : Raised by 1 NGO TAP

The triggers were set to run at a specific time and it was failing to execute for contacts.
Upon further investigation, we found that the query was timing out due to the collection size exceeding 15,000 contacts.

To resolve this issue, we optimized the query.

4) Different names appearing in contact list :

In the contact list and “Add to Collection” dropdown, we previously captured @contact.name.

We have now set a standard format for displaying contact names: we will first use @contact.fields.name; if that doesn’t exist, it will fall back to @contact.name, and if neither is available, it will show @contact.maskedPhone.
This ensures consistency across the application.

5) Contacts Not Appearing in “Add to Collection” :
Previously, when searching for a contact on the contact listing page for the collection, the contact was not visible.

Before Fix:

This bug has now been fixed, making contacts easily accessible when adding them to a collection.


After Fix :

Documentation Updated:

Existing Documentation Revamped:

1) Structured responses in GPT webhook functions:

Recently openAI added a new feature called structured responses in which we can give the expected response schema in the request itself, thus we can have responses in reliable json formats. We are leveraging this and parsing the response, if its json then add the key-value pairs to the results variable. Please take a moment to read through it.