Background jobs
Purpose
This page shows two things, read-only: (1) the background job records of plugins’ scheduled commands, and (2) the linked sign-in accounts and device information of a player you select. From this page you cannot start or retry a job, close a session or change a password. For those actions, use the Player profile page.
When to use
- To see whether a plugin’s scheduled job is running or has failed.
- To see which sign-in methods (Google, password and so on) a player is linked to the account with.
- To check which devices a player signed in from.
Step by step
Job records
- Make sure you selected the right game and environment.
- In the “Worker job runs” table, filter jobs by status: pending (not yet picked up, or released for a retry), claimed (a worker picked it up), done (completed), dead (closed because of a permanent error or the retry limit).
- For a specific time range, use the “Oluşturulma” (Created) column in the filter menu with “arasında” (between).
- The “Failure” column shows the error code of the failed job. The job content and the raw error text are not shown.
Player sign-in relations
- In the “Player auth relations” card, type and select the player in the Oyuncu (Player) field.
- Press İlişkileri getir (Fetch relations).
- The “Provider accounts” table shows the player’s linked sign-in accounts, and the “Devices” table shows device information and status. Revoked records are also listed. Long lists are paginated.
Note
The job runner’s health is not shown on this page: there is no persistent health signal source yet, so values such as “online” or lag are not made up. The “Worker health: gözlemlenemiyor” (Worker health: cannot be observed) card on the page says so.
Fields and options
| Field | Required | Description |
|---|---|---|
| Oyuncu (Player) | Yes (for İlişkileri getir) | The player whose relations will be seen |
Job records table
Plugin / mesaj (Plugin / message; the plugin ID, the message and the schedule ID), Durum (Status), Attempt (the number of attempts), Deadline (the last time), Failure (the error code) and Oluşturulma (Created) are shown by default. Sonraki deneme (Next attempt), Bitiş (End) and Zamanlama kimliği (Schedule ID) are turned on from the column menu.
Common situations
| Situation | What to do |
|---|---|
| It says “Operations yüzeyi yetki gerektiriyor” (The operations surface needs permission) | Your role has no job record read permission; ask an admin. |
| Player relations do not load | Player read permission is needed for this card; if you do not have it, you see a note. |
| A job is “dead” | The job closed with a permanent error or by reaching the retry limit. Look at the code in the Failure column together with the plugin’s owner; it cannot be restarted from the panel. |
| Job records are empty | There is no scheduled plugin job in the selected environment, or the filter is too narrow. |
| I want to close a device | This page is read-only; close sessions from the Player profile page. |