Theme
Castle Position Problems
What you see
An application link fails, a status is unclear, or an appointment differs from an earlier view.
What it usually means
The instance may be closed, the code invalid, the application updated, or a newer schedule published.
Safe checks and resolution
Use the latest link, confirm the instance, check My Appointments and the latest published schedule, then contact the kingdom organizer.
When to contact an authorized manager
Ask for help when the issue depends on role assignment, community scope, review status, or a locked workflow. Include the page name, visible message, selected scope, approximate time, and the safe steps already tried. Do not include passwords, tokens, private keys, or unrelated personal data.
Related guides
Practical depth
Check the appointment cycle
Compare kingdom, position, eligibility, capacity, application status, planner conflict, published version, and notice. A draft schedule is not authoritative.
Worked example, recovery, and limitations
What you see: An eligible applicant is placed on standby. Checks: Confirm kingdom cycle, linked-player review state, requested position, preferred time, resource relevance, compatible slots, row capacity, existing locks, and current draft. Decision: A full or incompatible row can leave an otherwise eligible candidate on standby. Recovery: An authorized planner may choose another compatible slot, keep standby, or adjust an unlocked draft placement, then rerun publish validation. A draft is not participant-facing and a published version is not silently editable. Include cycle, applicant, position, time, row, conflict, and version when contacting the organizer.
The output is a validated placement, explicit standby, gap, or conflict reason. Limitations include offline agreements and unsubmitted availability; never alter an applicant's declared inputs merely to fill capacity.
The planner cannot guarantee a globally optimal or politically fair schedule. Human review remains responsible for exceptional context, manual placement, publication, and communication through the latest version.
Approved application still looks unresolved
Check that approval completed and that any ambiguous player identity was resolved. Approval can now create or update the appropriate roster player, but it does not guarantee a slot. Reopen the candidate after the successful decision and check assignment and publication separately.
The planner should keep the selected kingdom and refresh its data without repeatedly restarting the page. If the Points area requests a kingdom that is already shown, verify the account and selector, then use the page refresh action. Report the visible mismatch without including private proof screenshots.
A guest plan has disappeared
The Local Castle Planner has no server recovery or account sync. Browser clearing or reset can remove its copy. Import your exported backup if you kept one. A temporary participant in a managed schedule is a different feature and follows that schedule's saving rules.