> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/management-api/license/scheduled-updates/update-scheduled-update.md).

# Update Scheduled Update

Update a Scheduled Update if the requesting manager has access permissions to it. Only `pending` and `failed` Scheduled Updates can be updated.

* `license` cannot be changed; it is ignored if sent.
* If `scheduled_update_data` is sent, it **replaces** all existing items of the Scheduled Update.
* Updating a `failed` Scheduled Update requires a new `scheduled_at` and sets its status back to `pending`, clearing `failed_at`.

**URL**: `/api/v1/scheduled-updates/{id}/`

**Method**: `PATCH`

## Parameters

| Parameter               | Type            | Requirements                                                                                                                                                                                       |
| ----------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `scheduled_at`          | Datetime        | Must be at least the next full hour. Truncated to the full hour. No other Scheduled Update may exist for the same license at that hour. Required when updating a `failed` Scheduled Update.        |
| `name`                  | String          | Maximum length: 255.                                                                                                                                                                               |
| `note`                  | String          |                                                                                                                                                                                                    |
| `scheduled_update_data` | List of objects | Between 1 and 100 items. Uses the same item format and validation as [Create Scheduled Update](https://docs.licensespring.com/management-api/license/scheduled-updates/create-scheduled-update.md) |

## Data example

```json
{
    "scheduled_at": "2026-11-02T00:00:00Z",
    "scheduled_update_data": [
        {
            "action": "license-update",
            "update_data": {
                "validity_period": "2027-12-01"
            }
        }
    ]
}
```

## Success Response

**Code**: `200 OK`

**Content examples**:

```json
{
    "id": 412,
    "license": 1593781720493289,
    "created_at": "2026-10-20T09:14:02.118274Z",
    "scheduled_at": "2026-11-02T00:00:00Z",
    "status": "pending",
    "applied_at": null,
    "cancelled_at": null,
    "failed_at": null,
    "name": "Q4 renewal",
    "note": "Extend validity and raise feature limit",
    "scheduled_update_data": [
        {
            "id": 1005,
            "action": "license-update",
            "product_feature": null,
            "product_custom_field": null,
            "update_data": {
                "validity_period": "2027-12-01"
            },
            "error_message": null
        }
    ]
}
```

## Error Responses

**Code**: `400 Bad Request`

```json
[
    "Only pending or failed scheduled updates can be updated."
]
```

```json
{
    "scheduled_at": [
        "scheduled_at is required when updating a failed scheduled update."
    ]
}
```

```json
{
    "scheduled_at": [
        "A scheduled update already exists for this license at this time."
    ]
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/management-api/license/scheduled-updates/update-scheduled-update.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
