Keyword search issue - doesn't return expected search result Issue Keyword search is not working on scenarios below: Use of task number as search term doesn't return records created in the last 24 hoursUsing meta data as search term doesn't return catalog item for Device Request Steps to Reproduce Open any list viewUse the search( on top of the list): for text = <keyword> (OR) Use the filter builder (funnel icon at the top-left): keywords are <keyword> In both cases, the search will not return the expected result. CauseWhenever there is a keyword search triggered, the system tries to fetch the result from 'ts_word', ts_document' tables(Enable 'Debug SQL' to find all involved tables). If the keyword is not present in ts_word or ts_document, the search will not return expected result. There can be many reasons for this issue to occur. One of those is stuck 'text_index' event (Go to the event log and check for 'text_index'. there shouldn't be more (>500)records ). For a keyword search, the system creates a 'text_index' event.These 'text_index' events are picked up and processed through a schedule named 'text index events process' which runs frequently at the backend.If 'text index events process schedule' is in 'ready' state, any idle schedule worker executes the schedule which processes the 'text_index' events.When this schedule is picked by a schedule worker, which is already stuck for is a long time by other transaction, the state of the schedule becomes 'queued' from 'ready'.Once it became 'queued', it will not be picked up by any other idle schedule worker. In case the stuck worker remains stuck, the schedule will never process.ResolutionTo resolve the issue, change the schedule's state from 'queued' to 'ready' manually from the list view. Do this several times (around 5-10 times), and if there is an available idle schedule worker, it will pick up the schedule and begin processing the events. If the issue keeps happening, it is necessary to identify the script that is causing the worker to become stuck and terminate it. Additionally, the script should be optimized to prevent it from keeping the workers occupied for an extended period. It should be noted that the process mentioned above may not be applicable to all keyword searches, as there may be other underlying causes and alternative methods for resolving the issue.Related LinksKB0713698: Contextual Search is not returning expected KB article KB1162299: Contextual search is not returning the expected results KB0745116: Keyword search not happening when reaches over the defined limit of Ts word