Bureaucrats, staff, Administrators
938
edits
Auto-creqing: Difference between revisions
Jump to navigation
Jump to search
→Automatic states
| (One intermediate revision by one other user not shown) | |||
| Line 87: | Line 87: | ||
|- | |- | ||
| failed-xml || 41 || | | failed-xml || 41 || | ||
|- | |||
| failed-db || 43 || | |||
|} | |} | ||
===Manual states=== | ===Manual states=== | ||
These states can only be set by moderators. They should be avoided as far as possible; keeping the dump ''used'' is preferred. | These states can only be set by moderators. They should be avoided as far as possible; keeping the dump ''used'' is preferred. | ||
{| class="wikitable" | {| class="wikitable sortable" | ||
|- | |- | ||
! State !! ID !! Description | ! State !! ID !! class="unsortable"|Description | ||
|- | |- | ||
| reset || 83 || A moderator wants the dump to be re-handled by the AVMF service, usually because he/she wants to unlock the related file temporarily. Lifecycle: new -> used -> reset -> new -> used. It would be better to improve/change the interface (regarding locks) instead of using this state. | | reset || 83 || A moderator wants the dump to be re-handled by the AVMF service, usually because he/she wants to unlock the related file temporarily. Lifecycle: new -> used -> reset -> new -> used. It would be better to improve/change the interface (regarding locks) instead of using this state. | ||