For performance reasons the search function does not search the production database directly, instead it searches an Index. To update that index - changes are queued up and then data is ingested - this can lead to a lag in data being made available to search. This lag can be a few seconds to several minutes depending on the amount of activity in the database (by all users). We continue to monitor and improve the efficiency of this process. If you are not finding your recent changes, it is likely that the search index has not ingested those changes. You can try the search again in a few minutes and hopefully your data is available in the search index.