Access / troubleshooting

Backend authentication error

A low-risk triage flow for access errors, with login queues, launch fixes, and account symptoms kept separate.

Needs verification

Short answer

Treat a backend authentication error as an access symptom first, not proof that local saves are broken. Capture the exact message and time, check the current patch and service signals, restart once, and compare the result with the login-queue and known-issues notes before taking any destructive action.

Start with the official launch patch notes, then compare current player reports in Steam Discussions. No community workaround should be presented as an official fix without a matching source.

Safe triage order

StepCheckRecord
1. MessageRead the exact backend/authentication wording.Screenshot or exact text, timestamp, and account state.
2. VersionCheck the installed build and whether a patch or hotfix is pending.Platform, build, storefront, and update status.
3. AccessTry one normal restart and compare online/login-queue behavior.Whether story/offline entry works and whether the error repeats.
4. EscalateReport a repeatable failure with evidence rather than deleting data.Network context, time window, platform, and steps to reproduce.

Do not mix these symptoms

QueueLogin queueLikely an access or service-capacity symptom; compare timing and server reports.
AuthBackend errorKeep the exact response text; it is more useful than a generic “servers down” label.
LocalCrash on launchUse the separate crash checklist instead of changing account or save data.
ProgressChallenge not trackingThat is a result/progression symptom and needs chapter and completion evidence.

What to send with a report

  1. Exact error.Use the visible text, not a paraphrase that could merge different failures.
  2. Platform and build.Keep PC, PlayStation, and Xbox reports separate unless the same source confirms a shared issue.
  3. Access comparison.State whether story mode, offline entry, or another account/device behaves differently.
  4. Time window.A service-side symptom can change quickly, so include the local time and timezone.

Backend authentication FAQ

What should I do first for a backend authentication error?

Capture the exact message and time, check the current patch or service notice, restart the game once, and compare with the login-queue and known-issues pages before changing saves or reinstalling.

Is a backend authentication error the same as a login queue?

Not necessarily. Both can block access, but the error text and timing should be recorded separately so a server queue is not confused with an account or backend response.

Should I delete local data or reinstall?

Do not start with destructive steps. Preserve the error text, platform, build, account state, and whether offline or story access works before escalating.