Optional Readonlyaac?: stringAccount-access-context token (from the dialog's Continue action, issued
in the same LRR context); chain it into the selection and code-submission
calls as aac.
Readonlychallenges: readonly AccountRecoveryBloksChallenge[]Recovery options the challenge picker offers ("Get code via email" / "Get code via WhatsApp" with the masked contact point).
Optional Readonlypreselected?: stringThe challenge the picker preselects (the observed server behavior preselects WhatsApp), when the screen names exactly one.
ReadonlyselectionServerParams: Record<string, unknown>server_params of the picker's Continue action — pass verbatim to
AccountRecoveryBloksSelectChallenge as selectionServerParams.
Readonly_Optional Readonly~effect/Optional Readonly~effect/Optional Readonly~effect/Optional Readonly~effect/Optional Readonly~effect/Optional ReadonlyaacAccount-access-context token (from the dialog's Continue action, issued
in the same LRR context); chain it into the selection and code-submission
calls as aac.
OptionalcauseReadonlychallengesRecovery options the challenge picker offers ("Get code via email" / "Get code via WhatsApp" with the masked contact point).
Optional ReadonlypreselectedThe challenge the picker preselects (the observed server behavior preselects WhatsApp), when the screen names exactly one.
Readonlyselectionserver_params of the picker's Continue action — pass verbatim to
AccountRecoveryBloksSelectChallenge as selectionServerParams.
Optionalstack
The login escalated to last-resort account recovery (LRR) instead of a session, a wrong password or 2FA: the server decided the login info is no longer connected to the account and offers a secure recovery process.
Loginalready performed the dialog's Continue step (the challenge-picker fetch) — exactly one extra request, as the app does when the user taps Continue — so the error carries the options that screen offers.