Fix ResourceNotFoundException

✅ Solution

ResourceNotFoundException in Elasticsearch usually means the resource (index, document, etc.) you're trying to access doesn't exist or hasn't been created yet. To fix this, ensure the resource is created *before* attempting to access it, perhaps by adding a step to create indices or waiting for asynchronous creation processes to complete before querying the data. Retrying the operation after a short delay often resolves the issue in situations where resource creation is still in progress.