BUG: GetMessageGateway Error on log in Screen when a paper filing Petitioner first attempts to verify their newly added email in DAWSON

[ttlenard]

Describe the Bug
A clear and concise description of what the bug is.
When a petitioner is verifying their email address when they initially switch from paper to electronic service, they get a GetMessageGateway error on the Login page. If they enter in their email and temporary password a second time, then it goes through just fine. The problem is that DAWSON doesn't seem to want to display that this petitioner has electronic service, even when they do in fact have it. The petitioner contact card still displays "No Email Provided". Petitioner has eAccess, but their email does not show up in the UI. This means that when something get's served on these cases, paper service is still occurring AND the petitioners are getting eService. See screen grabs below:

Business Impact/Reason for Severity
Petitioners continue to receive paper service even though they've agreed to electronic service, resulting in confusion, incorrect service, and increased workload for the court

In which environment did you see this bug?
TEST

Who were you logged in as?
Petitioner, Docket clerk, Admissions clerk

What were you doing when you discovered this bug? (Using the application, demoing, smoke tests, testing other functionality, etc.)
Testing

To Reproduce
Steps to reproduce the behavior:

1. Log in as an admissions clerk
2. Go to a case where a petitioner has paper service
3. Add in an email that you have access to as the petitioners email address (notice that the email address says pending, as it should)
4. Log out of DAWSON
5. Go to your email and find the "An account has been set up for you" email that got sent to you
6. log into DAWSON with the email and temporary password
7. Notice that you get the GetMessageGateway error message
8. Attempt to log in again, and it will work
9. Add in your permanent password
10. Go to your case and click on the parties tab
11. Notice that the petitioners contact card says "no email provided", but you have eAcces
12. Log out of DAWSON
13. Log into DAWSON as docket clerk
14. Navigate to the case and click on the party tab
15. Notice that the petitioner service preference is still set to paper

Expected Behavior
A clear and concise description of what you expected to happen.
When an admissions clerk adds in an email, and then the petitioner verifies it, the petitioner service preference should be set to electronic, and the email should be showing on their contact card.

Actual Behavior
A clear and concise description of what actually happened.
When an admissions clerk adds in an email, and then the petitioner verifies it, the petitioner service preference stays on paper, and the email that they just verified is showing as "no email provided"

Screenshots
If applicable, add screenshots to help explain your problem.
Error message I get after I enter in the petitioner email and temp password (my login defaults back to admissions clerk, but alas- I had entered in the petitioner login and temp password before)

This is me logged in as the petitioner. Look how it still says paper and no email provided, but I clearly can access my case electronically.

This person had gained eAccess, but when something get's served, it is still showing up that they have paper service:

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Cause of Bug, If Known

Process for Logging a Bug:

• Complete the above information
• Add a severity tag (Critical, High Severity, Medium Severity or Low Severity). See below for priority definition.

Severity Definition:

• Critical Defect
  Blocks entire system's or module’s functionality
  No workarounds available
  Testing cannot proceed further without bug being fixed.

• High-severity Defect
  Affects key functionality of an application
  There's a workaround, but not obvious or easy
  App behaves in a way that is strongly different from the one stated in the requirements

• Medium-severity Defect
  A minor function does not behave in a way stated in the requirements.
  Workaround is available and easy

• Low-severity Defect
  Mostly related to an application’s UI
  Doesn't need a workaround, because it doesn't impact functionality

Definition of Ready for Bugs(Created 10-4-21)

Definition used: A failure or flaw in the system which produces an incorrect or undesired result that deviates from the expected result or behavior. (Note: Expected results are use cases that have been documented in past user stories as acceptance criteria and test cases, and do not include strange behavior unrelated to use cases.)

The following criteria must be met in order for the development team to begin work on the bug.

The bug must:

• Be focused on solving a user problem
• Contain data for all fields in the bug template, so the team can pick it up and begin working immediately

Process: If the unexpected results are new use cases that have been identified, but not yet built, new acceptance criteria and test cases should be captured in a new user story and prioritized by the product owner.

If the Court is not able to reproduce the bug, add the “Unable to reproduce” tag. This will provide visibility into the type of support that may be needed by the Court. In the event that the Court cannot reproduce the bug, the Court will work with Flexion to communicate what type of troubleshooting help may be needed.

Definition of Done (Updated 4-14-21)

Product Owner

• Bug fix has been validated in the Court's test environment

Engineering

• Automated test scripts have been written
• Field level and page level validation errors (front-end and server-side) integrated and functioning
• Verify that language for docket record for internal users and external users is identical
• New screens have been added to pa11y scripts
• All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• Interactors should validate entities before calling persistence methods
• Code refactored for clarity and to remove any known technical debt
• Deployed to the Court's test environment