Backlog Task Manager
All 13 Unfiled 0 Backend Task 7
Docs Task 0
Frontend Task 0
Mobile App Task 6
News Letter Task 0
+ New folder

Add a task

+ Add notes

All tasks

13 open · 13 total
  • Fix "No Key Provided for Update" Error When Changing Country Code in Contact Update Backend Task Medium
    Added 1mo ago
    Notes
    🧑‍💼 WHO: POC ⚙️ WHAT: Fix the validation error "No key provided for update" that appears when users attempt to change the country code in the phone number field while updating a contact. 🚨 WHY: Users cannot update contact phone numbers by changing the country code because the system displays "No key provided for update" error preventing the contact from being saved. This blocks a basic contact management operation and creates poor user experience where changing country code triggers validation failure instead of accepting the update. The error indicates either missing validation logic that checks required fields before allowing update, incorrect form state handling where the key/ID is lost when country code changes, API expecting a field that's not being sent, or client-side validation incorrectly rejecting the update request. Users need to be able to update contact country codes without encountering validation errors to properly manage contact information.
  • Research Voice Calling Implementation and Its Server Infrastructure Impact Backend Task Medium
    Added 1mo ago
    Notes
    🧑‍💼 WHO: POC ⚙️ WHAT: Conduct comprehensive research into implementing voice calling functionality in Pabbly Chatflow including understanding technical requirements, server resource consumption patterns, bandwidth requirements, infrastructure costs, scalability challenges, and overall impact on existing server architecture and performance. 🚨 WHY: Need to understand whether adding voice calling functionality is feasible given current infrastructure, what server resources (CPU, memory, bandwidth, processing capacity) would be required, how voice calling would affect existing system stability and performance, what additional infrastructure investments would be needed, whether current servers can handle simultaneous voice calls plus existing webhook and API load, what latency and reliability implications exist, whether current database and caching systems would scale with call metadata, and what costs would be associated with implementing and maintaining voice calling at scale to make informed product decisions about feature feasibility and whether to pursue voice calling capability or focus optimization efforts elsewhere
  • 1.Implement the History Webhook for Syncing Old Contacts and Old Messages Backend Task Medium
    Added 1mo ago
← Prev Page 2 of 2 Next →