User Not Receiving Email OTP Prompt During Login ProcessIssue A user was not receiving the Email OTP prompt during the login process despite the correct MFA context and factor policy being configured to support Email OTP. The prompt never appeared for this user, but other test users with the same roles and configuration were able to complete MFA using Email OTP as expected.Symptoms1. Email OTP was not presented as a valid MFA factor during login for one specific user.2. The user was correctly assigned to the active MFA context.3. MFA was being enforced (mfa_enforced = true) as shown in the sys_user_login_history table.4. Other MFA factors (such as Authenticator App) were not configured or enabled for this user.5. Test users with the same group and role assignments were shown the Email OTP prompt successfully.ReleaseThis issue was observed in Yokohama but may not be specific to that release.CauseThe user's notification preference was disabled, which caused the system to ignore Email OTP as a MFA factor. Because of how the Email OTP factor is implemented in the MFA framework, if the notification cannot be delivered, the factor is not presented to the user at all. This is by design. Specifically, when a user attempts to authenticate using Email OTP, the system attempts to send the OTP via an outbound notification. If notifications are disabled for the user (via the user's Notification Preferences), the message would fail to send, and so the factor is not made available.ResolutionEnsure the user's notification settings are enabled:1. In the user's preferences, verify that Allow Notifications is enabled2. Ensure "Email" is configured as a valid delivery channel, has the users email address populated, and is enabled.3. Review any channel-specific notification preferences that might block email delivery.