> 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/vendor-platform/licenses/scheduled-license-updates/event-types-and-actions.md).

# Event Types & Actions

This page covers the full details of event types, statuses, field behavior, and available actions across all surfaces in Scheduled License Updates.

### Event Types

Each scheduled update is tagged with one or more type chips that describe what is being changed:

| Type                     | Description                                        |
| ------------------------ | -------------------------------------------------- |
| **License Update**       | A change to one or more license-level fields       |
| **License Reset**        | A reset of one or more license scopes              |
| **Feature Update**       | An add or edit of a product feature on the license |
| **Feature Removal**      | A removal of a product feature from the license    |
| **Custom Field Update**  | A change to a custom field value                   |
| **Custom Field Removal** | A removal of a custom field from the license       |

A single event can contain multiple types of changes. In that case, one chip per distinct type is shown.

### Event Statuses and Available Actions

| Status    | Apply now | Simulate | Edit | Cancel | Retry |
| --------- | --------- | -------- | ---- | ------ | ----- |
| Pending   | ✅         | ✅        | ✅    | ✅      | —     |
| Applied   | —         | —        | —    | —      | —     |
| Cancelled | —         | —        | —    | —      | —     |
| Failed    | —         | —        | ✅    | —      | ✅     |

### Changes Rail

While staging changes in the scheduling drawer, the **Changes rail** on the right shows a live summary of every staged change, with the current value and the new value it will be set to.

{% hint style="info" %}
The **before** values shown in the rail reflect the license at the time of scheduling,  not its state at the time the update is applied.
{% endhint %}

Individual changes can be removed from the rail using the **×** on each row. Tab badges show the count of staged changes per tab.

### Applying Changes Immediately

A **Pending** event can be applied before its scheduled time using **Apply now**. This applies all changes in the event immediately and moves the event to **Applied**.

### Failed Events

When an event fails, all changes are rolled back, nothing is applied. The failed event's card shows which item caused the error.

To recover a failed event:

1. Click **Edit** on the failed event
2. Correct the problematic value
3. Select a new future hour (the original time has passed)
4. Click **Save changes**  the event returns to **Pending**

### Cancelling Multiple Events

In the standalone list, select multiple **Pending** events using the row checkboxes and click **Cancel selected** to cancel them in bulk.

### Export

The **Export** action in the standalone list downloads a CSV of scheduled update data, including customer information. The export respects the active filters.

Exports are produced in **UTC**.

<figure><img src="https://1783554078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgLzurdfXUuKr9IziZWLz%2Fuploads%2FZCwNexPQfASQab5YdQa7%2Fimage.png?alt=media&amp;token=6fd8ace0-c9d2-4f35-82e9-f545eeed6c67" alt=""><figcaption></figcaption></figure>

### Audit Trail

Every scheduled update action  creation, edit, cancellation, application, and failure  is recorded in the license's **Logs** tab, providing a full audit trail of who scheduled what and when.

### Availability

Scheduled License Updates is a platform feature that must be enabled for your account. If the feature is not enabled:

* The **Scheduled updates** sidebar link is not shown
* The **Scheduled updates** tab on individual licenses is not shown
* The standalone Scheduled updates page displays a **Scheduled updates are not available** message


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.licensespring.com/vendor-platform/licenses/scheduled-license-updates/event-types-and-actions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.