Meilisearch icon

Meilisearch

Consume Meilisearch API

Actions33

Tasks → Wait for Task

AI-generated

Overview

This node operation waits for a specific task to complete in Meilisearch by polling the task status until it is either succeeded, failed, or canceled. It is useful in scenarios where subsequent workflow steps depend on the completion of an asynchronous task in Meilisearch, such as indexing or document updates. The node supports configurable polling intervals with optional exponential backoff to reduce API calls, and a timeout to limit the maximum waiting time.

Use Case Examples

  1. Waiting for a document indexing task to complete before proceeding with a search query.
  2. Polling a task that updates index settings to ensure changes are applied before continuing.

Properties

Name Meaning
Task UID The unique identifier of the task to wait for.
Use Exponential Backoff Enables gradual increase of polling interval to reduce API calls over time.
Polling Interval (ms) Fixed interval between polling requests in milliseconds, used when exponential backoff is disabled.
Initial Polling Interval (ms) Starting interval between polling requests in milliseconds, increases by 1.5x every 5 attempts when exponential backoff is enabled.
Max Polling Interval (ms) Maximum interval between polling requests when exponential backoff is enabled; polling interval will not exceed this value.
Timeout (seconds) Maximum time to wait for task completion in seconds before throwing a timeout error.

Output

JSON

  • status - The final status of the task (e.g., succeeded, failed, canceled).
  • taskUid - The unique identifier of the task being waited on.
  • type - The type of the task.
  • details - Additional details about the task result or failure.

Dependencies

  • Meilisearch API with authentication credentials

Troubleshooting

  • If the task does not complete within the specified timeout, a timeout error is thrown indicating the task UID and timeout duration. Increase the timeout or check the task status externally.
  • Incorrect Task UID input will cause the node to fail to find the task; ensure the UID is correct and corresponds to an existing task.
  • Network or authentication issues with the Meilisearch API will cause HTTP request failures; verify API credentials and network connectivity.

Links

Discussion