-
Type:
Bug
-
Resolution: Done
-
Priority:
High
-
Affects Version/s: 2.1
-
None
-
FLW Sprint 25, FLW Sprint 26, FLW Sprint 27
-
FLW Mobile App
-
Prod
There is a ABHA count mismatch between ABDM dashboard and AMRIT report,
Suspected reasons:
ABHA is created using native ABDM APIs and after that ABHA is saved in the AMRIT by calling an AMRIT API, may be due to poor network in the field sometimes or most of the times this AMRIT API might be failing.
Steps to Reproduce:
Open FLW App on mobile or Tab device .
Login and navigate to "Create ABHA" screen
Expected Result:
User should able to Create ABHA and send ABHA to saved in the AMRIT
Actual Result:
Sometimes created ABHA numbers are Not saving in AMRIT
- is duplicated by
-
AMM-1609 API related to save and mapping HealthID To Beneficiary id is poor due to network latency
-
- Closed
-
- relates to
-
AMM-1493 Prod_Assam_ABHA ID count issue_DB and DASHBOARD
-
- Closed
-
-
AMM-1609 API related to save and mapping HealthID To Beneficiary id is poor due to network latency
-
- Closed
-
-
FLW-269 Log firebase events for tracking ABHA APIs
-
- Closed
-
-
FLW-299 Implement sync ABHA details to AMRIT from local db
-
- Closed
-
-
AMM-1636 Niramay-II Wrong Providerservicemapid under ABHA table
-
- Closed
-
-
AMM-1637 Niramay-II Beneficiary RegistrationID null under m_benhealthidmapping
-
- Closed
-