Overview
This node performs the "DeleteItem" operation on the Recombee recommendation service. It deletes items from a Recombee database by their unique item IDs. This is useful in scenarios where you want to remove outdated, irrelevant, or incorrect items from your recommendation catalog to keep recommendations accurate and up-to-date.
Practical examples include:
- Removing discontinued products from an e-commerce recommendation engine.
- Deleting content that is no longer available or relevant in a media recommendation system.
- Cleaning up test or placeholder data from the recommendation database.
The node supports batch deletion with retry logic to handle transient failures gracefully.
Properties
| Name | Meaning |
|---|---|
| Item ID | The unique identifier of the item to delete from the Recombee database. |
| Max Retries | Number of times to retry failed batch requests when deleting items (default is 2 retries). |
Output
The node outputs an array of JSON objects, each corresponding to an input item processed. Each output object contains:
success: A boolean indicating whether the deletion succeeded for that item.itemId: The ID of the item attempted to be deleted.data: If successful, contains the response data from Recombee for the deletion request.error: If failed, contains the error message returned by Recombee or encountered during processing.
If the node is configured to continue on failure, it will output success/failure per item without stopping the entire execution. Otherwise, it throws an error on the first failure.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Recombee service.
- Needs configuration of the Recombee database ID, private token, and region via credentials.
- Uses the official Recombee API client library to communicate with the Recombee service.
- Supports a configurable timeout for API requests, defaulting to 10 seconds if not set.
Troubleshooting
Common issues:
- Invalid or missing item IDs will cause deletion errors.
- Network or authentication failures can cause batch requests to fail.
- Exceeding rate limits or sending too large batches may result in errors.
Error messages:
- Errors returned from Recombee are surfaced per item. For example, "Item not found" indicates the item ID does not exist.
- If retries are exhausted, the node throws an error unless "continue on fail" is enabled.
Resolutions:
- Verify that item IDs are correct and exist in the Recombee database.
- Check API credentials and permissions.
- Adjust "Max Retries" to handle intermittent network issues.
- Use smaller batch sizes if encountering rate limit errors (the node batches up to 100 items per request).