- Issue created by @tgoeg
- 🇸🇮Slovenia agile-mark-l
I believe this was covered in other issues, previously merged into the 2.x branch.
- Status changed to Closed: outdated
4 months ago 9:34am 28 August 2024
As seen in 🐛 Primary key inference fails for Meilisearch >=1.x and fields ending in "id" (includes patch) Fixed , there may be errors in Meilisearch that do not propagate properly into Drupal and Admins/Devs can have a hard time in finding out what went wrong without any messages/logs indicating that.
See the steps in 🐛 Primary key inference fails for Meilisearch >=1.x and fields ending in "id" (includes patch) Fixed for example.
For any tasks sent to Meilisearch, query their status and log their errors to the debug log. Depending on the task, it might be feasible to wait for it to finish and show a notification about a potential error right away as well, but this may block for too long.
Closed: outdated
2.0
Code
I believe this was covered in other issues, previously merged into the 2.x branch.