Troubleshooting Access and Blocked Actions

Most blocked actions are deliberate server decisions. Diagnose the category before retrying.

Login or session trouble

1. Return to Character Home.
2. Confirm whether the shell shows Log In or an Avatar.
3. Log in again if the session expired.
4. On a shared device, log out fully before another person signs in.

Missing authority

• Confirm the Avatar.
• Confirm Acting-As is the intended Entity.
• Confirm current membership standing when the action depends on it.
• Use the Workbench surfaced by navigation; a missing Workbench is meaningful.
• Remember that Acting-As does not grant authority.

Empty results

• Clear optional filters.
• Check spelling and try an alias.
• Confirm the content or Card is active and visible to your audience.
• Remember that restricted titles and counts are intentionally absent.

Failed or uncertain action

Do not submit repeatedly. Capture:

• route and section;
• visible subject label;
• safe operation or contract identifier;
• approximate local time;
• exact user-facing status or block reason;
• whether the owning route shows the effect.

Never collect or send passwords, cookies, session identifiers, raw payment credentials, or private article bodies.

Pick the right surface

• Field Manual: how to operate active behavior.
• Console: what runtime events occurred.
• Laboratory: experimental models and unresolved design.
• Codex: developer contracts and internal documentation.

Read Field Manual, Laboratory, Codex, and Console for the full boundary.