Recover from temporary sign-in service failures
A temporary current-member service failure is reported as unavailable and can be retried. It no longer masquerades as a successful signed-out check or an expired private API session.
- Improvements and fixes
Session failure classification: Member-provider server, gateway, throttling and unknown network failures return a sanitized503 instead of a200 signed-out result or a401 private API rejection. Explicit authentication, denial and missing-member outcomes still deny access. Every retry reads current identity and saved authority; no stale-authority fallback is introduced.
- New
Recoverable Arabic and English feedback: The shared client offers a selected-language retry message. Temporary failures do not trigger sign-in navigation, clear the last known account or resend writes. Protected views remain concealed until a successful fresh check; real sign-out, revocation and changed-account behavior remain enforced.
The misclassification was reproduced and repaired through the real HTTP handler using a synthetic provider failure. This does not establish the root cause or resolution of the previously observed intermittent Wix504. No failure is injected into production. Independent real-role, network/location/device and provider-delivery acceptance remain separate. No account, access grant, invitation, message, financial/source edit or policy activation is introduced.