---
title: Update
slug: klevu-magento-v4/entities-update
docTags: 
createdAt: 2024-08-06T15:29:11.351Z
---

:::hint{type="warning"}
Entity update does not send any data via the API to Klevu.

Its only purpose is to update the `klevu_indexing_entity` database table and calculate the `next_action`.
:::


Entity Update triggers Entity Discovery for a selection of entity IDs.
Various plugins and observers trigger entity updates, e.g. when an entity is saved.

Entity update will:

- add any missing entities and determine if those entities are indexable.
- set any of the passed entity IDs which are no longer indexable, but were previously registered, to have a `next_action` of `Delete`.
- set any of the passed entity IDs that have become indexable to have a `next_action` of `Add`.
- set the `next_action` for the passed entity IDs to `Update` if they are indexable.

Entity update will **NOT**:

- send any data to Klevu.

`\Klevu\Indexing\Service\EntityUpdateOrchestratorService` responsible for entity update. All the above methods of triggering entity update use this service.

### CLI

`klevu:indexing:entity-update`

The update can also be triggered via CLI and has 1 required parameter and 2 optional parameters

- `entity-ids` - a comma-separated list of entity IDs to update
- `api-keys` - \[optional] comma-separated list of API keys to update
- `entity-types` - \[optional] comma-separated list of entity types to update,
  options:
  - `KLEVU_PRODUCT`
  - `KLEVU_CATEGORY`

e.g

```shell
bin/magento klevu:indexing:entity-update \
    --entity-ids="1,2,3" \
    --entity-types="KLEVU_PRODUCT" \
    --api-keys="klevu-example-js-api-key" 

```