Restart and wipe schedules

The Schedules page contains two independent tools:

• Restart schedules start or restart the server at planned times.
• Wipe schedule changes DayZ storage according to a recurring or one-time schedule.

Use the preset daily, weekly, or monthly controls unless you specifically need a custom expression. Presets are easier to review and less likely to run at the wrong time.

Create a restart schedule

1. Select New.
2. Set Scheduled restarts to On.
3. Choose Daily, Weekly, Monthly, or Custom Expression.
4. Complete the time/day fields and verify Timezone. For Custom Expression, wait for the panel to validate the draft and review the description, timezone, and Next scheduled runs before continuing.
5. Choose the restart policy.
6. Select Create.
7. Confirm the schedule appears under Saved restart schedules.

Your service can limit the total number of restart schedules, how many may be enabled, and the minimum interval between runs.

Restart schedule options

Option	Meaning
Scheduled restarts	Enables or disables this schedule without deleting it.
Frequency — Daily	Runs once every day at the selected local time.
Frequency — Weekly	Runs on one or more selected weekdays at the selected local time. At least one day stays selected.
Frequency — Monthly	Runs on the selected day of the month at the selected local time. A schedule for day 29, 30, or 31 will not run in a month that lacks that date.
Frequency — Custom Expression	Uses the exact Quartz expression you enter, six fields plus an optional seventh for the year. The panel validates it and previews future runs.
Time (local)	Hour 0–23 and minute 0–59 in the selected timezone.
Timezone	The IANA timezone used to calculate future runs, such as Europe/Stockholm or America/Chicago. The form starts with your browser timezone.
Skip when busy	Skips a run when another server operation is already active instead of competing with it. Recommended.
Start if offline	Starts an offline server when the schedule runs. Turn this off if an intentionally stopped server must stay offline.

Scroll to see all columns →

Select Edit beside a saved schedule to load it into the form, then select Update. Delete permanently removes that schedule. The list also shows whether it is enabled, its timezone, and its last result when available. Custom schedules show their readable description when one is available, falling back to the expression.

Use a custom restart expression

Custom restart expressions use Quartz order:

seconds minutes hours day-of-month month day-of-week

An optional seventh field for the year may follow day-of-week. Omit it to repeat without restricting the year.

For example, this represents 04:00 every Monday in the selected timezone:

0 0 4 ? * MON

Custom expressions are exact

Quartz syntax differs from common five-field Linux cron. Use Daily, Weekly, or Monthly when possible. A valid-looking expression can still run more often than intended.

Validate and preview before saving

As you edit the custom expression or Timezone, the panel checks the current draft. A valid expression shows a plain-language description and up to three entries under Next scheduled runs in the selected timezone, each with its UTC offset. These times are not converted to your browser timezone.

• Checking schedule… means validation is still pending. Create or Update stays disabled until the current custom expression and timezone validate successfully.
• A validation error means the expression or timezone must be corrected. Five-field Linux cron is not accepted.
• If the check cannot complete, select Retry after the connection recovers.
• This expression has no future run times. means the syntax is valid but nothing is upcoming, for example when an optional year is already in the past. Adjust the expression if it should run again.

Examples in the selected timezone:

Expression	Meaning
0 0 4 ? * *	Daily at 04:00.
0 0 0/4 ? * *	Every four hours, starting at midnight.
0 0 4 ? * MON	Mondays at 04:00.

Scroll to see all columns →

A preview neither saves nor runs a schedule. Actual runs still depend on Skip when busy, Start if offline, and your service’s limits, so review the displayed UTC offsets when planning around clock changes.

This live validation and preview applies to restart schedules. The wipe form remains a separate workflow with its own timing and confirmation controls.

Configure a wipe schedule

Storage wipes remove game data

A full or partial wipe can permanently remove world or player progress. Confirm the selected server, make a usable backup, and schedule downtime before enabling a wipe.

1. Load the current page and review the selected server name.
2. Set Scheduled wipes to On.
3. Choose Recurring cron or One-time wipe.
4. Complete the schedule and select a Wipe type.
5. Review every Before wipe and After wipe option.
6. Tick I understand this changes the server wipe schedule.
7. Select Save and wait for Synced.

Changing any wipe field clears the confirmation checkbox so you must review the final draft again.

Wipe timing options

Option	Meaning
Scheduled wipes	Enables or disables execution while preserving the saved settings.
Schedule mode — Recurring cron	Repeats according to a daily, weekly, monthly, or custom schedule.
Schedule mode — One-time wipe	Runs once at the chosen local date/time.
Frequency — Daily	Builds a daily schedule at the selected time.
Frequency — Weekly	Builds a schedule for the selected weekday or weekdays.
Frequency — Monthly	Builds a schedule for the selected day of the month. Months without that date are skipped.
Frequency — Custom Expression	Uses the six-field expression exactly as entered.
Time (your local time)	Converts the displayed hour and minute for the host schedule using the clock information supplied by the panel.
Run once at (your local time)	Stores a single future run from the local date/time you select.

Scroll to see all columns →

The custom wipe field uses this six-part order shown by the panel:

seconds minutes hours day-of-month month day-of-week

Wipe types

Wipe type	Effect
Full Wipe	Requests the panel’s full storage-wipe mode. Review the confirmation for the exact target.
Player Database Only	Requests the player-database wipe mode. Verify the file scope in the confirmation before saving.
Persistence Only	Requests the persistence wipe mode. Verify the file scope in the confirmation before saving.

Scroll to see all columns →

The confirmation shown by the panel is the authority for the files affected. Back up both player and persistence data if the scope is unclear, and do not continue until the confirmation matches the reset you intend to run.

Before and after options

Option	Meaning	Recommendation
Stop server	Stops the game server before the wipe runs.	Keep on so files are not being written during deletion.
Create backup	Requests a backup before the wipe.	Keep on and verify the backup file list is configured.
Start server	Starts the server after the wipe workflow finishes.	Keep on for normal automated maintenance; turn off for manual inspection.
Disable after wipe	Turns off this wipe configuration after it runs.	Turn on for a one-off/reset workflow that must not repeat.

Scroll to see all columns →

Create backup depends on the backup configuration and file list in Advanced settings. Do not assume the checkbox produced a useful backup without checking the Backups page.

Safer rollout

1. Create a manual backup and verify it is listed.
2. Announce the maintenance time with its timezone.
3. Save a disabled schedule first and review its displayed values.
4. Enable it only after confirming the wipe type and before/after actions.
5. After the planned run, check the schedule result, server status, backups, and DayZ logs.

If the page says restart schedules are unavailable but wipe schedules still load, do not try to recreate the restart through a wipe. Contact support so the service can be updated.