> 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/events-api/event-list/scheduled-update-events.md).

# Scheduled Update Events

Events emitted as scheduled license updates are created, changed, simulated, and processed.

A scheduled update is a set of license changes that LicenseSpring applies at a scheduled hour.

See [Scheduled License Updates](https://docs.licensespring.com/vendor-platform/licenses/scheduled-license-updates.md) for configuration details. Every event includes the `scheduled_update` object defined in [event data objects](https://docs.licensespring.com/events-api/event-list/event-data-objects.md).

{% hint style="info" %}
A scheduled update can have the status `pending`, `applied`, `cancelled`, or `failed`. The cancellation event is spelled `scheduled_update.canceled`, with one `l`.
{% endhint %}

### Event reference

#### `scheduled_update.created`

**Sent when:** a scheduled update is created, one at a time or in bulk (one event per update).

{% hint style="info" %}
If a license already has a scheduled update for the same hour, the new changes are added to that update. This event uses the existing update's `id`.
{% endhint %}

#### `scheduled_update.updated`

**Sent when:** a scheduled update that is `pending` or `failed` is edited. The list of changes in the event is the full new list.

#### `scheduled_update.canceled`

**Sent when:** a pending scheduled update is canceled, one at a time or in bulk (one event per update).

**Not emitted when:** A scheduled update is deleted. Deletion emits no event.

#### `scheduled_update.simulated`

**Sent when:** someone previews a pending scheduled update (Simulate). Nothing is changed.

**Event data:** `status` shows the predicted result, `applied` or `failed`. Each change's `error_message` explains a predicted failure. Neither is saved.

#### `scheduled_update.will_process_1_day`

**Sent when:** a pending scheduled update is due within the next 24 hours. LicenseSpring checks every hour, so **this event is sent every hour until the update is applied, up to 24 times for the same update.** An update created less than an hour before it is due may get none.

**Event data:** `scheduled_update`, plus `future_scheduled_update` with the predicted `status`, `applied` or `failed`, and `errors`, a list of error messages.

{% hint style="warning" %}
If this event triggers a reminder or task, track the scheduled update `id`. Handle each update only once.
{% endhint %}

#### `scheduled_update.processed`

**Sent when:** LicenseSpring tried to apply a scheduled update, at its scheduled hour or when someone applies it now or retries a failed one. Check `status`: `applied` if every change was applied, `failed` if any change failed. A failed update changes nothing: all its changes are rolled back, and the failing change has an `error_message`.

**Not emitted when:** A retry of a failed update fails again.

{% hint style="warning" %}
Changes made by a scheduled update do not emit `license.updated` or other license events. `scheduled_update.processed` is the only notification.
{% endhint %}


---

# 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/events-api/event-list/scheduled-update-events.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.
