Skip to main content

Server errors

Journal​

Open Journal -> Server Errors to review failed game connections and operations. The summary shows errors, reviewed and unreviewed entries, and affected servers. Below it are a chart, reason and server breakdowns, and the entry list.

Each entry shows the time, server, connection, operation, reason, suggested action and ID. Use the time and server to locate the corresponding game logs. Clearing an entry does not resolve the underlying failure.

The summary and entry list use the same period and filters.

The project and game server lists show a warning when there are unreviewed errors. Its link opens the journal with that review filter selected.

Filters​

The default period is Last 30 days. Select a different preset or enter your own dates. Both boundary dates are included in UTC.

FieldSelection
ServerOne game server or all available servers.
ReasonFor example, access denied, unavailable, or a game build mismatch.
Review statusAll, reviewed or not reviewed.
ConnectionLogin server, game database or game commands.
OperationConnect, prepare request, read data or another operation.
GroupingAutomatic or a chosen calendar interval for the chart.
Entries per page10, 25, 50 or 100 entries.
Entry IDFind a specific error.

Apply the selection with the funnel button. Reset restores the initial filters. Previous and Next appear when other pages are available; paging does not change the summary for the entire selected period.

A single reason is selected, with a suggested settings check in each entry.

Reviewing Entries​

Select entries and click Mark selected as reviewed. The header checkbox selects only unreviewed entries on the current page. Opening the journal does not mark anything as reviewed.

The review action is enabled after entries are selected.

Reviewed entries remain in the journal with the review time. The mark means someone has examined the entry, not that the issue is resolved.

Use the review filter to distinguish new entries from those already examined.

Retention​

The Retention tab controls automatic cleanup and its retention period in days. The default is 90 days. Entries older than this period are removed whether reviewed or not. Reducing the period makes older entries eligible for the next cleanup.

Click Save to apply changes.

Turn off Automatic cleanup and save to keep entries until they are manually cleared. Increasing the period or disabling cleanup does not restore entries already removed.

The retention period field is disabled while automatic cleanup is off.

Manual Cleanup​

Open Clear entries, select servers and a period, then click Preview cleanup. This step does not delete anything.

The cleanup selection is separate from the journal filters.

Check the servers, dates and entry count in the confirmation window. Cancel closes it without deleting anything. Clear entries starts deletion, which cannot be undone. A preview remains valid for 15 minutes; prepare it again after it expires. Confirmation is disabled for an empty selection.

Check the selection before confirming: deleted entries cannot be restored.

After confirmation, the page shows the cleanup status and number removed. Refresh the status or open the history to follow its progress. Errors arriving after the preview are not included in that selection.

Cleanup History​

Cleanup history lists manual and automatic cleanups, including who initiated them, servers, period, status, times and selected and removed counts. The actual removed count can be lower if another cleanup has already deleted some of the selected entries.

The history retains the result of a confirmed cleanup.

Permissions And Recovery​

Staff group permissions separately control viewing errors, marking entries as reviewed, clearing entries and changing retention settings. Clearing requires its own permission; journal access alone is not enough. Retention is read-only for staff without permission to change it.

If no entries match, change the period or reset the filters. Retry a temporarily unavailable action later. If a selection is no longer available, refresh the journal; prepare a new preview before clearing it.

No matching errors is different from a failed report load.