Restart and wipe schedules

Schedules has two tools that operate independently:

Restart schedules starts or restarts the server at times you set.
Wipe schedule modifies DayZ storage on a repeating schedule or once.

Prefer the daily, weekly or monthly presets when they meet your needs. They are easier to check than a custom expression and reduce scheduling mistakes.

Create a restart schedule

Choose New to open a schedule draft.
Turn Scheduled restarts On.
Select Daily, Weekly, Monthly or Custom Expression.
Fill in the time/day controls and check Timezone. For Custom Expression, wait for validation and review the description, timezone and Next scheduled runs.
Set the restart policy you want.
Press Create.
Check the new entry in Saved restart schedules.

Service limits may cap the number of saved or enabled restart schedules and set a minimum interval between runs.

Restart schedule options

Option	Meaning
Scheduled restarts	Turns execution on or off while retaining the schedule.
Frequency — Daily	Executes once each day at the chosen local time.
Frequency — Weekly	Executes at the chosen local time on selected weekdays. At least one weekday must remain selected.
Frequency — Monthly	Executes on the chosen monthly date and local time. Dates 29, 30 or 31 are skipped in months that do not contain them.
Frequency — Custom Expression	Takes a Quartz expression with six fields and an optional seventh year field. The panel validates the expression and previews its runs.
Time (local)	Sets hour `0–23` and minute `0–59` for the chosen timezone.
Timezone	Sets the IANA zone for future runs, such as `Europe/Stockholm` or `America/Chicago`. Your browser timezone is the initial selection.
Skip when busy	Prevents a scheduled run from competing with a server operation in progress. Recommended.
Start if offline	Allows a run to start a stopped server. Disable it when a server stopped on purpose must remain offline.

Scroll to see all columns →

Open a saved schedule with Edit, then save the revised form with Update. Delete removes it permanently. The list includes enabled state, timezone and the latest result where available. Custom entries show a readable description or, if none is available, the expression.

After creating or updating a schedule, check its saved entry for the time and timezone you intended. The draft form can still show different values. A recorded success refers to a past run, so check the upcoming runs separately.

Use a custom restart expression

Write custom restart expressions in Quartz field order:

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

You may add a seventh year field after day-of-week. Leave it out to repeat without a year restriction.

For a run every Monday at 04:00 in the selected timezone, use:

0 0 4 ? * MON

Validate and preview before saving

Editing the expression or Timezone starts validation of that draft. Valid input produces a description and up to three Next scheduled runs, each with a UTC offset. The preview uses the selected timezone without converting it to your browser timezone.

Checking schedule… indicates pending validation. Create and Update remain disabled until the current expression and timezone pass.
Correct the expression or timezone after a validation error. The panel rejects five-field Linux cron.
Once the connection is restored, choose Retry if validation could not finish.
This expression has no future run times. means valid syntax schedules nothing in the future, such as a year field set in the past. Edit it if more runs are intended.

These examples use the selected timezone:

Expression	Meaning
`0 0 4 ? * *`	Runs each day at 04:00.
`0 0 0/4 ? * *`	Runs at 00:00, 04:00, 08:00, 12:00, 16:00 and 20:00 in the selected timezone.
`0 0 4 ? * MON`	Runs at 04:00 on Mondays.

Scroll to see all columns →

Previewing does not save or execute the schedule. Actual execution still follows Skip when busy, Start if offline and service limits. Check preview UTC offsets when planning across clock changes.

These expressions name local clock times. Confirm the upcoming dates and offsets around daylight-saving changes; scheduler versions can handle missing or repeated local times differently. Keep restart and wipe windows separate so one maintenance operation can finish before the next begins.

These validation and preview controls are for restart schedules. Wipes have separate timing and confirmation controls.

Configure a wipe schedule

Load the page and verify the selected server name.
Keep Scheduled wipes Off while preparing the draft.
Select Recurring cron or One-time wipe.
Set the timing and choose a Wipe type.
Check each Before wipe and After wipe setting.
After confirming the affected files, future execution time and usable backup, turn Scheduled wipes On and tick I understand this changes the server wipe schedule.
Press Save and wait until the form shows Synced.

Editing a wipe field clears the confirmation checkbox. Review the final draft before confirming again.

Wipe timing options

Option	Meaning
Scheduled wipes	Switches execution on or off without discarding saved settings.
Schedule mode — Recurring cron	Repeats using daily, weekly, monthly or custom timing.
Schedule mode — One-time wipe	Executes once at the local date and time you select.
Frequency — Daily	Creates a run each day at the chosen time.
Frequency — Weekly	Creates runs on the selected weekday or weekdays.
Frequency — Monthly	Creates a run on the chosen day of each month, skipping months that lack that date.
Frequency — Custom Expression	Uses your six-field expression without changing it.
Time (your local time)	Converts the shown hour and minute into a host schedule using the panel’s clock information.
Run once at (your local time)	Records one future run using your chosen local date and time.

Scroll to see all columns →

Enter custom wipe timing in the panel’s six-field order:

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

Wipe types

Wipe type	Effect
Full Wipe	Selects the provider’s full storage-wipe mode. Confirm the affected paths before enabling it.
Player Database Only	Selects player-database wiping. Confirm which database files it targets.
Persistence Only	Selects persistence wiping. Confirm which world files it targets and what remains.

Scroll to see all columns →

Read your service’s wipe specification or ask support which paths the wipe deletes. The label and confirmation checkbox won’t give you that file list. Keep Scheduled wipes Off until you know it matches the reset you intend and your backup includes the affected data.

Before and after options

Option	Meaning	Recommendation
Stop server	Stops the game process before deletion.	Leave enabled to prevent writes during the wipe.
Create backup	Requests a recovery copy before deletion.	Leave enabled and check that the backup file list is configured.
Start server	Starts the game after the wipe workflow.	Keep enabled for scheduled maintenance, or disable it for a manual inspection.
Disable after wipe	Disables this wipe configuration following execution.	Enable for a one-off reset that must not repeat.

Scroll to see all columns →

Configure backups and their file list in Advanced settings for Create backup to work. After it runs, check the copy on Backups and confirm it contains the files you need. Enabling the option alone won’t tell you whether the backup succeeded.

Safer rollout

Take a manual backup, verify its file list and download a recovery copy. Follow DayZ backup and restore to check a copy in a separate test instance.
Tell players the maintenance time and timezone.
Save the schedule disabled and inspect the displayed settings.
Confirm wipe type and before/after actions before enabling execution.
Once the run is due, inspect its result, server state, backup copies and DayZ logs.

If restart scheduling is unavailable while wipe scheduling still works, contact support about the service. Do not substitute a wipe for a restart.