Logic correction for the language selection and the user onboarding flow.

[Sachinbisht27]

Describe the bug We are experiencing some discrepancies for the users who are changing their program and language details after completing the registration.

Add diagnosis details

1. Multiple user groups:
   • Once the Language selection is completed.
   • The user is getting added to the user group for the selected language by DRY-FLOW.
   • The user again changes the language ID by placing the missed call.
   • Which is adding him to another user group as well.
2. Program ID and time selection details not updating in the database:
   • Once the onboarding is completed the program details didn't update on the database.
   • The user program and time category can be changed by the user multiple times on the onboarding day.

Steps to reproduce the behavior For multiple user group issues:

1. Complete the user onboarding by selecting the upcoming time slot.
2. Run the DRY-FLOW.
3. Place a missed call and update the language ID.
4. Then run the DRY-FLOW again.
5. Check the user is added to how many groups.

For data sync issue:

1. Complete the user onboarding by selecting all the prompts.
2. Once the data is updated to the database and the registration is marked as completed.
3. Place a missed call again and change the program and time details.
4. Check if the details are updating in the database properly or not.

Expected behavior

• [x] The user should be removed from the earlier user groups if the user is updating the language ID later.
• [x] The program and Time slot details should be updated on the database if the user is changing it on the same day of onboarding.

Screenshot;

Root cause User Onboarding Logic.

Impact

• 500 - 800 users
• Mostly the affected users are new users changing the language and program details.

Action items

• [x] Write down all the test cases that can happen while user onboarding.
• [x] Figure out the root cause for the issue.
• [x] Test all the cases thoroughly.
• [x] Share the changes with the team.

Criticality

• Medium

Acceptance Criteria

• [x] The cause for the issue should be diagnosed.

Documentation Add whatever documentation will be required here.

[thebelrobot]

Observations so far:

1. Most of the users who got added to a wrong language group had a common behaviour of multiple onboarding requests.
2. I have tried dry running multiple workflows, but was not able to reach a situation where my number is added to a wrong language group.
3. In my try run I was able to re-create the scenario.

[Sachinbisht27]

• [x] Write down all the test cases that can happen during user onboarding.
  • [x] User switching from HINDI to BHOJPURI.
  • [x] User switching from HINDI to AWADHI.
  • [x] User switching from BHOJHPURI to AWADHI.
  • [x] User switching from BHOJHPURI to HINDI.
  • [x] User switching from AWADHI to HINDI.
  • [x] User switching from AWADHI to BHOJHPURI.

Diagnosis sheet for the affected users:

https://docs.google.com/spreadsheets/d/1iWay43QC4aG80Dr1hksZ66BN54l9TIohBkrdkyX-h3Y/edit?usp=sharing

[Sachinbisht27]

The root causes for the issue with the action item to fix:

Diagnosis:

Completed users are signing up again

• The alumni users are re-signing into the programs.
• The program is getting started for the users again at RapidPro with the selected program option.
• The data is not getting updated in the database for such users as their registration status is completed.

Target issue:

• 479

New users giving other responses than expected.

• The new users are first selecting Program 1.
• Then users again started the onboarding flow and exited the flow without selecting any program.
• In this case, the first selected program 1 is going for the user from the next day from RapidPro.
• But the program details are updating in the database as DEFAULT values.

Target issue:

• 478

Users changing language.

• The onboarding flow is removing the user from the Lang-Dost-Pilot-Intro group.
• The users should be removed from all content groups if added for the user.

Target issue:

• 479

For already affected users:

Target issue:

• 480

[Sachinbisht27]

We will be targeting the Fix for the diagnosed issues in separate GitHub tasks:

• 478 @Sachinbisht27

• 479 @kritirakheja @Sachinbisht27

• 480 @Sachinbisht27

[Sachinbisht27]

Closing as diagnosis is completed and we are targeting all action items in separate issues.