trouble indexing new/changed content

I'm sorry to have not replied yet. I haven't forgotten about this, it has just been difficult to find time to investigate. I have a ticket open for it in and intend to get to it before too much longer.

It still exists with the version 8.x-1.34.

This case is specific to unpublished items with moderation state change, as described by @ultrabob on #7. And may not be related to the issue reported by the OP.

Also, I should point out that our search index include unpublished content, which has multiple moderation states (draft, A, B, C... etc). We use a filter in the view configuration page to exclude unpublished content with the moderation state "draft" (but not others).

I have observed the following:

• The index includes all drafts, as we wanted ✅
• The index updates immediately after saving a draft ✅
• The index is correctly updated by entityUpdate() call, as evident by its timestamp ✅
• The moderation state of the indexed item updates if the value is the same as that of the original (e.g. from A to A). ✅
• The moderation state of the indexed item reverts to the initial state (draft) if the state values are different after updating (e.g. from A to B). As a result, the item did not show up in search, as we would want it to. ❌

Workaround

When I turn off “Index items immediately”, the moderation state of the item updates correctly after cron runs. I also reduce the cron frequency to 1 minute so that users can see the item more quickly.

On a fresh install, I can no longer reproduce the issue described earlier. The search index updates _almost_ as expected, with a caveat:

In order for the search index to update the moderation state value correctly, "Default revision" must be checked for any custom moderation state. Otherwise:

If the item was Published and a user sets the moderation state to something else (such as "awaiting greenlight"), the search index will not update the moderation state. This can be problematic.

However, as the fix seems to be in setting "Default revision" for a state in the Workflow configuration, so I wonder how the Search API module can take that into account.

Sorry for going off topic, as my comment again is related to moderation states.

Tested on:

- Fresh install of Drupal 10.4
- Install meilisearch (ddev)
- Install and enable search_api module (1.38)
- Install and enable search_api_meilisearch module (2.0)
- Enable Workflows, Content Moderation
- Set up basic workflows:
- Moderation state: Awaiting greenlight
- Transition: All states to "Awaiting greenlight"