Summary
When the user uses browser back from the timeout error to retry, the styled email input still appears, but the OTP email that follows arrives in the default unstyled template. The client identifier is no longer in scope at OTP-send time even though the form looks branded.
Reproduce
- Steps 1-3 from issue 1 (reach the timeout error page).
- Browser back to the styled email input.
- Submit email.
Actual
OTP delivered using the default email template. Client branding (subject, header, footer) is missing.
Expected
The OTP email retains the original client's template, matching what the user received on the first attempt of the same flow.
Notes
Summary
When the user uses browser back from the timeout error to retry, the styled email input still appears, but the OTP email that follows arrives in the default unstyled template. The client identifier is no longer in scope at OTP-send time even though the form looks branded.
Reproduce
Actual
OTP delivered using the default email template. Client branding (subject, header, footer) is missing.
Expected
The OTP email retains the original client's template, matching what the user received on the first attempt of the same flow.
Notes
clientIdneeded to resolve the email template is gone for the same reason it's gone for error-page CSS.clientIdforward another way).