--- title: "putScheduledUpdateGroupAction" slug: "cli-vautoscaling-autoscalinggroup-putscheduledupdategroupaction" tags: ["Auto Scaling", "VPC"] updated: 2026-10-08T04:54:05Z published: 2026-10-08T04:54:05Z canonical: "cli.ncloud-docs.com/cli-vautoscaling-autoscalinggroup-putscheduledupdategroupaction" --- > ## Documentation Index > Fetch the complete documentation index at: https://cli.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # putScheduledUpdateGroupAction Available in VPC Create or edit a scaling schedule for Auto Scaling Group. You can set one-time and repeated execution schedules. ## Syntax The `putScheduledUpdateGroupAction` syntax is as follows: ``` ./ncloud vautoscaling putScheduledUpdateGroupAction \ --autoScalingGroupNo \ --minSize | --maxSize | --desiredCapacity \ [--scheduledActionNo ] \ [--scheduledActionName ] \ [--startTime ] \ [--endTime ] \ [--recurrence ] \ [--timeZone ] \ [--regionCode ] \ [--output ] ``` ## Options This section describes the options available when running `putScheduledUpdateGroupAction`. ### Required options The following options are required for `putScheduledUpdateGroupAction`. | Options | Type | Required | Description | | --- | --- | --- | --- | | `--autoScalingGroupNo` | String | Required | Auto Scaling Group number - See [getAutoScalingGroupList](/docs/en/cli-vautoscaling-autoscalinggroup-getautoscalinggrouplist). | | `--minSize` | Integer | Conditional | Minimum number of servers in the Auto Scaling Group - `0`-`30` - Set to a value less than or equal to `maxSize`. - Enter `0` if you do not want to retain any servers. - At least one among `minSize`, `maxSize`, or `desiredCapacity` must be entered. | | `--maxSize` | Integer | Conditional | Maximum number of servers in the Auto Scaling Group - `0`-`30` - Set to a value greater than or equal to `minSize`. - At least one among `minSize`, `maxSize`, or `desiredCapacity` must be entered. | | `--desiredCapacity` | Integer | Conditional | Desired number of servers in the Auto Scaling Group - Set to a value between `minSize` and `maxSize`. - The number of servers is automatically adjusted based on the input value. - At least one among `minSize`, `maxSize`, or `desiredCapacity` must be entered. | | `--scheduledActionNo` | String | Conditional | Schedule number - Do not enter when creating a schedule. - When editing a schedule, either `scheduledActionNo` or `scheduledActionName` must be entered. - See [getScheduledActionList](/docs/en/cli-vautoscaling-autoscalinggroup-getscheduledactionlist). | | `--scheduledActionName` | String | Conditional | Schedule name - Enter a new name to create a new schedule. - Enter 1-255 characters, including lowercase English letters, numbers, and special character `-`. - The string must start with a lowercase English letter and end with a lowercase English letter or a number. - Edits the schedule when an existing name is entered. - Required when creating a schedule. - When editing a schedule, either `scheduledActionNo` or `scheduledActionName` must be entered. - See [getScheduledActionList](/docs/en/cli-vautoscaling-autoscalinggroup-getscheduledactionlist). | | `--startTime` | Date | Conditional | Schedule start date and time - `yyyy-MM-ddTHH:mm:ssZ` format. - Must be set to a time after the current time and before `endTime`. - Required when not setting `recurrence`. - If `recurrence` is set, the earliest recurring schedule after `startTime` is executed. - If only `recurrence` is set, the earliest recurring schedule is executed at `startTime`. - Can't overlap with the start time of another schedule. | ### Optional options These are the optional options for `putScheduledUpdateGroupAction`. Options that are not specified will use their default values. | Options | Type | Required | Description | | --- | --- | --- | --- | | `--endTime` | Date | Optional | Schedule end date and time - `yyyy-MM-ddTHH:mm:ssZ` format. - Must be set to after `startTime`. - If `recurrence` is set, recurring executions will stop after that time. | | `--recurrence` | String | Optional | Recurrence settings - crontab format (minute, hour, day, month, day of the week) - Minute: `0`-`59` - Hour: `0`-`23` - Day: `1`-`31` - Month: `1`-`12` or English name - Day of the week: `0`-`7` or English name (`0`=`7`=Sunday) - `*`: Select all - Examples - Every hour on the hour: `0 * * * *` - Every Saturday at 16:30: `30 16 * * 6` - Midnight on the 1st of every month: `0 0 1 * *` - Midnight on January 1st every year: `0 0 1 Jan *` | | `--timeZone` | String | Optional | Reference time zone - You can specify the time zone for recurrence settings. - `KST` (default) \| `UTC` - `KST`: UTC+9 - `UTC`: UTC+0 | ### Common options For information on options commonly used in the `vautoscaling` command, see [Auto Scaling (VPC) options](/docs/en/cli-vautoscaling#%EC%98%B5%EC%85%98). ## Examples If the request to create or edit a scaling schedule is successful, the configuration information for the scaling schedule is returned. ### Command The command example is as follows: ``` ./ncloud vautoscaling putScheduledUpdateGroupAction \ --autoScalingGroupNo 20461037 \ --scheduledActionName schedule-01 \ --minSize 0 \ --maxSize 2 \ --desiredCapacity 1 \ --startTime 2026-12-01T03:00:00+0900 \ --regionCode KR \ --output json ``` ### Output The output example is as follows: ``` { "putScheduledUpdateGroupActionResponse": { "totalRows": 1, "scheduledUpdateGroupActionList": [ { "autoScalingGroupNo": "20461037", "scheduledActionNo": "13650027", "scheduledActionName": "schedule-01", "minSize": 0, "maxSize": 2, "desiredCapacity": 1, "startTime": "2026-12-01T03:00:00+0900", "recurrence": "", "timeZone": "KST" } ], "requestId": "e1f2a3b4-c5d6-7890-efab-123456789012", "returnCode": "0", "returnMessage": "success" } } ```