KPI Sync

Date: 2025-07-03 · Duration: 19.850000381469727 min Organizer: Nader Attendees: Nader, Ahmad, Mike, Martin

Summary

• Ahmadreza reported successful URL extraction with 50 out of 200 tested URLs returning status 200, while 151 resulted in 404 errors.
• Regex implementation for URL parameters took longer than anticipated; faster progress expected on query and body parameters now that methodology is established.
• Pay engine scraper is undergoing upgrades to improve error catching, focusing on enhancing adapter output processing.
• 404 errors identified as likely due to incorrect URLs or missing parameters like merchant IDs, while 400 errors suggest missing required parameters or authentication.
• Manual inspection of API responses is necessary to distinguish between URL and parameter issues since both yield similar error codes.
• All fixes are being applied to YAML files to preserve data integrity, moving away from CSV output.
• Generic API types are now standardized with default GET methods for consistency in API testing procedures.
• Martin’s QA testing on the chat product uncovered two UI bugs: one affecting interface functionality with valid responses, and another preventing first-time users from typing.
• Completion of URL validation is targeted before the next meeting to ensure a solid project foundation.
• Subsequent steps include extraction of path parameters and implementation of query and body parameters after successful URL validation.

Action Items

• Ahmadreza Abdoli Complete URL testing and validation to ensure all extracted URLs are correct (09:50) Implement path parameters extraction after URL validation is finished (08:19) Proceed with query parameters and body parameters implementation (08:19)

Martin Elias Costa Create tickets for the two UI bugs found during chat product QA testing (11:35) Share created ticket links in team Slack channel to avoid duplication (12:20) Notify Raymond about the identified UI issues (11:35)

Nader Atrchin Create tickets for production QA findings and assign to appropriate team members (12:01) Create ticket for first-time chat UI typing issue (13:45) Post all QA ticket links in team chat for visibility (12:01)