Check system status
시스템 상태 (System status) shows when each repository was last collected successfully. Start here if student activity counts have stopped changing or look unusual. Only administrators can open this screen.
Collection runs automatically at the top of every hour, and every Sunday at 03:00 it rereads everything. You normally do not need to check this screen unless someone reports unusual numbers.
Read collection status
Section titled “Read collection status”- Open
시스템 상태(System status) in the관리자(Administrator) group on the left. - Check the badge on the
수집 상태(Collection status) card at the top. - If the badge is not
정상(Normal), read the description under it, then find the지연(Delayed) repositories in수집 대상 상세(Collection target details).
The badge is one of 정상 (Normal), 지연 (Delayed), or 추적 대상 없음 (No tracked targets). The card also shows the 추적 저장소 (Tracked repositories) and 지연 저장소 (Delayed repositories) counts and 다음 주기 예상 (Expected next cycle).
The badge is chosen by checking the table below from top to bottom. The first matching badge is shown.
| Badge | Meaning | Screen description |
|---|---|---|
추적 대상 없음 (No tracked targets) |
There are no repositories to collect yet. | Asks you to check whether the collection app is installed in the program GitHub organization and whether repositories are registered. |
지연 (Delayed) |
At least one repository last succeeded more than 2 hours ago. | Asks you to find the delayed repositories in 수집 대상 상세 (Collection target details) and, if they stay delayed after the next cycle, to check the collection app installation and permissions. |
정상 (Normal) |
None of the above applies. | None |
A repository that fails is not held back; the next hourly collection simply tries it again. After one failure it can show 지연 (Delayed) for a few minutes just before the next hourly collection, and it returns to 정상 (Normal) when that collection succeeds. If it fails again, it stays 지연 (Delayed).
The screen does not describe how to escalate a lasting stall to the service operator or developer. Policy confirmation needed
What each card shows
Section titled “What each card shows”데이터 최신성(Data freshness):마지막 수집 성공(Last successful collection) is the most recent successful collection time among organization repositories, with its age (for example,3시간 전, 3 hours ago).수집 대상 상세(Collection target details): For each repository registered to a team, it shows마지막 수집 성공(Last successful collection) and a state of정상(Normal),지연(Delayed), or수집 전(Not collected yet). Delayed repositories come first, and the top shows delayed and total counts, such as지연 1 / 전체 5(Delayed 1 / Total 5). A repository is not registered or collected automatically just because it belongs to the organization.외부 저장소 수집(External repository collection): This is collection for student personal repositories. If there are targets, it shows the tracked count and마지막 수집 성공(Last successful collection). If there are no targets, it shows수집 대상 학생 개인 저장소가 없습니다(There are no student personal repositories to collect). External collection is configured to run with organization collection at the top of every hour.
When the screen is narrow, the right columns of 수집 대상 상세 (Collection target details) are cut off. Scroll the table sideways or widen the window.
Run collection now
Section titled “Run collection now”Collection runs automatically on a schedule, but you can start it immediately when needed. Click 지금 수집 실행 (Run collection now) at the top right to receive a notification that the request was accepted. Collection takes time; wait for 마지막 수집 성공 (Last successful collection) to change. You do not need to click repeatedly.
A gray button with a 수집 중 (Collecting) badge means collection is already running. Wait until it finishes before trying again. While the request is being sent, 실행 요청 중… (Requesting execution…) appears briefly.