[{"data":1,"prerenderedAt":29},["ShallowReactive",2],{"doc-en-schedule-automatic-restart":3},{"path":4,"slug":5,"title":6,"description":7,"category":8,"subcategory":9,"icon":10,"date":11,"author":12,"order":13,"image":14,"tags":15,"keywords":20,"docGroup":26,"docGroupIcon":26,"link_fr":27,"bodyHtml":28},"\u002Fdocs\u002Fen\u002Fautres\u002Fpanel-gaming\u002Fschedule-automatic-restart","schedule-automatic-restart","How to Schedule Automatic Restarts with Schedules","Set up automatic restarts for your Winheberg gaming server using Schedules and CRON syntax, no command line needed.","autres","panel-gaming","tabler:file-text","2026-07-24","Winheberg",35,"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart.webp",[16,17,18,19],"schedule","cron","automatic restart","gaming panel",[21,22,23,24,25],"automatic restart schedule","cron gaming panel","automatic server restart","pterodactyl schedule","winheberg gaming panel","","\u002Fdocs\u002Fpanel-gaming\u002Fschedule-redemarrage-automatique","\u003Ch2>Context\u003C\u002Fh2>\n\u003Cp>Keeping a game server stable over time sometimes requires restarting it regularly. Memory builds up, some resources leak, and certain changes only take effect after a full restart. Rather than doing it manually, the Winheberg panel offers a scheduling system called \u003Cstrong>Schedules\u003C\u002Fstrong>, which lets you automate these actions at set intervals.\u003C\u002Fp>\n\u003Cp>This guide explains how to set up an automatic restart CRON task from the Winheberg panel, with no command line or outside intervention needed.\u003C\u002Fp>\n\u003Ch2>What is a Schedule?\u003C\u002Fh2>\n\u003Cp>A Schedule is a scheduled task tied to your server in the panel. It relies on CRON syntax, a standard format for precisely defining when an action should run (every hour, every night at 3am, every Monday, etc.). Each Schedule can chain several actions in a specific order, with a delay between each one.\u003C\u002Fp>\n\u003Ch2>Prerequisites\u003C\u002Fh2>\n\u003Cp>You need an active server on the Winheberg panel and to be logged in with an account that has access to Schedule management.\u003C\u002Fp>\n\u003Cdiv class=\"markdown-alert markdown-alert-note\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cline x1=\"12\" y1=\"16\" x2=\"12\" y2=\"12\"\u002F>\u003Cline x1=\"12\" y1=\"8\" x2=\"12.01\" y2=\"8\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>If your account is a sub-user, check that the \u003Cstrong>Schedules\u003C\u002Fstrong> permission has been enabled by the server owner.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch2>1. Access Schedules\u003C\u002Fh2>\n\u003Cp>Log in to the Winheberg panel, then select the relevant server.\u003C\u002Fp>\n\u003Cp>In the left side menu, click \u003Cstrong>Schedules\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967464478-f5bd3bd3feaff35c0fce4c5c.webp\" alt=\"Schedules menu in the Winheberg panel\" width=\"400\" \u002F>\n\n\u003Ch2>2. Create a Schedule\u003C\u002Fh2>\n\u003Cp>Click \u003Cstrong>Create Schedule\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967485384-534b3623a76a2cd676f87271.webp\" alt=\"Create Schedule button\" width=\"800\" \u002F>\n\n\u003Ch3>2.1 Name the task\u003C\u002Fh3>\n\u003Cp>Give your Schedule a clear name, for example \u003Ccode>auto-restart\u003C\u002Fcode>. This name is purely for your own reference in the list.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967508340-18c9efb5b2bdeaa5181751ea.webp\" alt=\"Schedule name field\" width=\"800\" \u002F>\n\n\u003Ch3>2.2 Set the frequency\u003C\u002Fh3>\n\u003Cp>Next, enter the execution frequency in CRON format. This format is made up of five fields representing minutes, hours, day of the month, month, and day of the week, respectively.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967526167-901e0a6d39764ea5cf8057c3.webp\" alt=\"CRON frequency configuration\" width=\"800\" \u002F>\n\n\u003Cp>The table below lists the most commonly used expressions.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Frequency\u003C\u002Fth>\n\u003Cth>CRON expression\u003C\u002Fth>\n\u003Cth>Description\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Every hour\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0 * * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>At the start of every hour\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every 2 hours\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0 *\u002F2 * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Every 2 hours\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every night at 3am\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0 3 * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Daily nightly restart\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every morning at 6am\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0 6 * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Daily morning restart\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every Monday at 4am\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0 4 * * 1\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Weekly task\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Every 30 minutes\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>*\u002F30 * * * *\u003C\u002Fcode>\u003C\u002Ftd>\n\u003Ctd>Frequent restart\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cdiv class=\"markdown-alert markdown-alert-tip\">\u003Cspan class=\"alert-icon\">\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\">\u003Ccircle cx=\"12\" cy=\"12\" r=\"10\"\u002F>\u003Cpath d=\"M12 16v-4\"\u002F>\u003Cpath d=\"M12 8h.01\"\u002F>\u003C\u002Fsvg>\u003C\u002Fspan>\u003Cdiv class=\"markdown-alert-body\">\u003Cp>The \u003Cstrong>Show Cheatsheet\u003C\u002Fstrong> button in the panel displays a quick reference for CRON syntax if you're not familiar with this format.\u003C\u002Fp>\n\u003C\u002Fdiv>\u003C\u002Fdiv>\n\u003Ch3>2.3 Additional options\u003C\u002Fh3>\n\u003Cp>Two options are available before confirming.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Only when server is online\u003C\u002Fstrong> runs the task only if the server is already started. This option is recommended to avoid an unnecessary restart if the server is already stopped.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Schedule enabled\u003C\u002Fstrong> turns the task on or off. Leave it enabled so the Schedule starts working as soon as it's created.\u003C\u002Fp>\n\u003Cp>Click \u003Cstrong>Create Schedule\u003C\u002Fstrong> to confirm.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967541891-c7b8602e67ac474b43d2d621.webp\" alt=\"Confirming the Schedule\" width=\"800\" \u002F>\n\n\u003Ch2>3. Add the stop task\u003C\u002Fh2>\n\u003Cp>Once the Schedule is created, click \u003Cstrong>Manage Schedule\u003C\u002Fstrong> to access its tasks.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967555801-4b58b42ff6da4d19ccab572b.webp\" alt=\"Manage Schedule button\" width=\"800\" \u002F>\n\n\u003Cp>Click \u003Cstrong>New Task\u003C\u002Fstrong> to add the first action.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967570480-1ac88c54f5684b701d4da6cf.webp\" alt=\"New Task button\" width=\"800\" \u002F>\n\n\u003Cp>Set up the task with the following parameters.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>Value\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Action\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>Send power action\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Time offset\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>0\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Payload\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>Stop the server\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>Click \u003Cstrong>Create task\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967591328-aaa12c087fdc2312274fbb1a.webp\" alt=\"Stop task configuration\" width=\"800\" \u002F>\n\n\u003Ch2>4. Add the start task\u003C\u002Fh2>\n\u003Cp>Add a second task via \u003Cstrong>New Task\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967700359-0608644618e58cd4728801e0.webp\" alt=\"Adding the start task\" width=\"800\" \u002F>\n\n\u003Cp>Set up the task with the following parameters.\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>Value\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Action\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>Send power action\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Time offset\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>30\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Payload\u003C\u002Ftd>\n\u003Ctd>\u003Ccode>Start the server\u003C\u002Fcode>\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>The 30-second offset gives the server enough time to shut down cleanly before the start is triggered. Click \u003Cstrong>Create task\u003C\u002Fstrong> to confirm.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967608653-b2a5615ef9291bc304408a14.webp\" alt=\"Start task configuration\" width=\"800\" \u002F>\n\n\u003Ch2>Result\u003C\u002Fh2>\n\u003Cp>Your Schedule is now active. The server will stop and then restart automatically according to the frequency you set, with no action needed on your part.\u003C\u002Fp>\n\u003Cimg src=\"\u002Fstatics\u002Fimages\u002Fdocs\u002Fen\u002Fpanel-gaming\u002Fschedule-automatic-restart-1779967623932-199cebc26b2a3b631a2dfbc0.webp\" alt=\"Active Schedule with both tasks configured\" width=\"800\" \u002F>\n\n\u003Ch2>If you run into trouble\u003C\u002Fh2>\n\u003Ch3>❌ The Schedule is active but the server doesn't restart\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Check that \u003Cstrong>Only when server is online\u003C\u002Fstrong> isn't checked if your server was stopped at the time it was meant to run\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The server restarts immediately without stopping first\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>The start task's Time offset is likely set to \u003Ccode>0\u003C\u002Fcode>, change it to \u003Ccode>30\u003C\u002Fcode> to give the stop time to finish\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ The Schedule doesn't run at all\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Check that \u003Cstrong>Schedule enabled\u003C\u002Fstrong> is turned on\u003C\u002Fli>\n\u003Cli>Check that the CRON expression is valid\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>❌ Access denied to Schedules\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>If you're a sub-user, ask the server owner to enable the corresponding permission in the account settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Best practices\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Pick a quiet restart time\u003C\u002Fstrong>, ideally at night or early morning, to minimize the impact on connected players. A daily nightly restart at 4am or 5am is often a good compromise\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Avoid overly short intervals\u003C\u002Fstrong> (every 5 or 10 minutes) unless you have a specific need, since it leaves players little time to reconnect and can disrupt the gaming experience\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Back up important data\u003C\u002Fstrong> before restarting if your server holds inventories or progress. Some games offer a save command you can trigger with a \u003Cstrong>Send command\u003C\u002Fstrong> task added before the stop task\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Give each Schedule a clear name\u003C\u002Fstrong> if you create several, this makes maintenance easier and avoids mixing up tasks\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Need help?\u003C\u002Fh2>\n\u003Cp>If your Schedule doesn't trigger, if the server doesn't restart in the expected order, or if you're unsure about the CRON syntax to use, our team is here. Open a ticket in the \u003Cstrong>Technical\u003C\u002Fstrong> department from your client area, fill in the \u003Cstrong>Related Product\u003C\u002Fstrong> field with the server in question, and specify the Schedule's name along with the behavior you observed.\u003C\u002Fp>\n\u003Cp>Your server is now set up to restart automatically, with no action needed on your part 🎮\u003C\u002Fp>\n",1788993140230]